From d222f6ecdf7ce65c3e11eaeb0695936f42ddbd96 Mon Sep 17 00:00:00 2001 From: Dustin Byrne Date: Thu, 29 Oct 2026 16:14:43 -0400 Subject: [PATCH] docs(mcp): clarify unsigned session token trust --- posthog/mcp/session_token.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/posthog/mcp/session_token.py b/posthog/mcp/session_token.py index 228c0a593..ac2b38593 100644 --- a/posthog/mcp/session_token.py +++ b/posthog/mcp/session_token.py @@ -6,8 +6,9 @@ So at ``initialize`` we mint that header as a token carrying the session id and client identity -- any pod can read them back from the header alone. -The token is unsigned: it holds only what the client already self-reports. It is -wire-compatible with the TypeScript SDK (same short keys ``sid``/``cn``/``cv``/``pv``), +The token is unsigned, so clients can change its contents. Use decoded values +for analytics, not authentication or authorization. It is wire-compatible with +the TypeScript SDK (same short keys ``sid``/``cn``/``cv``/``pv``), so a token minted by one SDK decodes in the other. """