List all annotation queues for human review.
AI agents call get_annotation_queues to retrieve information from Langfuse Mcp Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of existing annotation queues without creating, modifying, or deleting any data. It is a straightforward read operation that queries the state of annotation queues. The blast radius if misused (e.g., by an AI agent listing all queues) is minimal, as it only exposes metadata about existing queues without altering system state.
From the tool's definition Tool name 'get_annotation_queues' and description 'List all annotation queues for human review' indicate a retrieval/query operation with no data modification or side effects.
Attacks that exploit this kind of access
List all annotation queues for human review. It is categorised as a Read tool in the Langfuse Mcp Python MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Mcp Python MCP server in PolicyLayer and add a rule for get_annotation_queues: 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 Python. Nothing to install.
get_annotation_queues 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_annotation_queues 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_annotation_queues. 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_annotation_queues is provided by the Langfuse Mcp Python MCP server (log-logn/langfuse-mcp-python). 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 →