Get a specific session by ID including its traces.
AI agents call getSession to retrieve information from Langfuse Mcp Extended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves session data and associated traces from Langfuse without altering, creating, or destroying any data. It is a read-only query operation with no side effects, fitting the 'Read' category. Severity is low because unauthorized access to session traces, while potentially exposing debug information, does not enable direct system compromise or data destruction.
From the tool's definition Tool name is 'getSession' and description states 'Get a specific session by ID including its traces' - explicit retrieval operation with no modification, creation, or deletion.
Attacks that exploit this kind of access
Get a specific session by ID including its traces. It is categorised as a Read tool in the Langfuse Mcp Extended MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Mcp Extended MCP server in PolicyLayer and add a rule for getSession: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Langfuse Mcp Extended. Nothing to install.
getSession is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getSession rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for getSession. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
getSession is provided by the Langfuse Mcp Extended MCP server (langfuse-mcp-extended). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →