List all available filter fields for fetching Langfuse traces.
AI agents call list_langfuse_trace_filters 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 and enumerates filter field options, a read-only operation with no side effects. It poses minimal risk as it only returns schema/metadata information that helps construct queries, similar to introspection endpoints. Confidence is high because the intent is unambiguously informational.
From the tool's definition Tool name contains 'list' and description states 'List all available filter fields' — a query operation that retrieves metadata about filtering capabilities without modifying data or triggering external operations.
Attacks that exploit this kind of access
List all available filter fields for fetching Langfuse traces. 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 list_langfuse_trace_filters: 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.
list_langfuse_trace_filters 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 list_langfuse_trace_filters 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 list_langfuse_trace_filters. 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.
list_langfuse_trace_filters 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 →