get_langfuse_trace_detail
AI agents call get_langfuse_trace_detail to retrieve information from Langfuse Trace Fetcher without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical observability trace data without modifying it. The 'detail' suffix suggests it fetches specific trace records by query or ID. No side effects, mutations, deletions, or external operations are indicated. The lack of a tool description slightly reduces confidence, but the server context and naming conventions clearly position this as a read operation for debugging and monitoring purposes.
From the tool's definition Tool name 'get_langfuse_trace_detail' indicates retrieval of trace observability data. The server description states it 'Fetches Langfuse observability traces' and enables 'querying and viewing trace data', confirming read-only access patterns.
Attacks that exploit this kind of access
get_langfuse_trace_detail. It is categorised as a Read tool in the Langfuse Trace Fetcher MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Trace Fetcher MCP server in PolicyLayer and add a rule for get_langfuse_trace_detail: 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 Trace Fetcher. Nothing to install.
get_langfuse_trace_detail 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_langfuse_trace_detail 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_langfuse_trace_detail. 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_langfuse_trace_detail is provided by the Langfuse Trace Fetcher MCP server (karandeepsinghsodhi/skill-to-fetch-traces). 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 →