Repository navigation
docs(mcp): clarify unsigned session token trust - #1151
Conversation
There was a problem hiding this comment.
Not approved — this change needs a human reviewer.
Re-adding the stamphog label gives the same result unless the changed files change.
stamphog won't auto-review this pull request because two gates refused it. The deny-list gate flagged posthog/mcp/session_token.py as matching the auth category, and the tier gate classified the change as T2-never, a category that is never handled automatically, even though it is only 5 lines in 1 file. The size and prerequisites gates passed, but they don't override the refusal.
The author can ask a human reviewer to look at it, since files in sensitive areas need human sign-off no matter how small the change is.
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✗ | matches: auth |
| size | ✓ | 5L, 1F substantive — within ceiling |
| tier | ✗ | classified as T2-never: T2-never (5L, 1F, single-area, docs) |
| stamphog 2.6.1 | .stamphog/policy.yml @ unknown · reviewed head d222f6e |
posthog-python Compliance ReportDate: 2026-10-29T20:19:51.494513+00:00 ✅ All Tests Passed!121/121 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
Motivation and Context
Clarify that clients can modify unsigned MCP session tokens and that decoded values are for analytics, not authentication or authorization.
Fixes #1126.
How did you test it?
Agent context
Autonomy: Human-driven (agent-assisted).
Prepared with Pi using Git/GitHub CLI, pytest, and Ruff. Reviewed with the code-review workflow before opening this PR.