Fetch traces with flexible filtering options.
AI agents call get_traces to retrieve information from Langfuse MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trace data from Langfuse analytics with filtering capabilities. It performs a query operation that returns existing data without creating, modifying, deleting, or executing side effects. Traces are observability/logging data, not financial or sensitive operational controls. The flexible filtering options are read-only query parameters.
From the tool's definition Tool name is 'get_traces' with description 'Fetch traces with flexible filtering options.' The verb 'Fetch' indicates data retrieval without modification or execution of external operations.
Attacks that exploit this kind of access
Fetch traces with flexible filtering options. It is categorised as a Read tool in the Langfuse MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Langfuse MCP Server MCP server in PolicyLayer and add a rule for get_traces: 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 Server. Nothing to install.
get_traces 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 get_traces 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 get_traces. 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.
get_traces is provided by the Langfuse MCP Server MCP server (therealsachin/langfuse-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 →