[Langfuse] List sessions with pagination. Sessions group related traces together.
AI agents call langfuse_list_sessions to retrieve information from Shepherd MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries session data from Langfuse observability backend. It has no side effects—it only returns existing session metadata and does not create, modify, delete, or execute operations. The blast radius is minimal as it only exposes observability/debugging data.
From the tool's definition Tool description explicitly states 'List sessions' with pagination. The verb 'list' and the read-only nature of querying session metadata from an observability provider indicate no data modification, deletion, or code execution occurs.
Attacks that exploit this kind of access
[Langfuse] List sessions with pagination. Sessions group related traces together. It is categorised as a Read tool in the Shepherd MCP MCP Server, which means it retrieves data without modifying state.
Register the Shepherd MCP server in PolicyLayer and add a rule for langfuse_list_sessions: 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 Shepherd MCP. Nothing to install.
langfuse_list_sessions 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 langfuse_list_sessions 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 langfuse_list_sessions. 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.
langfuse_list_sessions is provided by the Shepherd MCP server (neuralis-in/shepherd-mcp). 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 →