Add an official mirror queue entry to the regular MCP implementation queue. This creates a draft MCP implementation from the mirror data. This is an async operation. This action: 1. Creates a new draft MCP implementation using the mirror
AI agents use add_official_mirror_to_regular_queue to create or update resources in Langfuse Observability — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Langfuse Observability environment.
The tool performs a creation operation that produces new data (draft MCP implementation) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. The async nature and draft status indicate the changes can be undone or modified. This fits the Write category (creates or modifies data reversibly).
From the tool's definition 'Add an official mirror queue entry to the regular MCP implementation queue. This creates a draft MCP implementation from the mirror data.' - The tool creates new data (a draft MCP implementation) from existing mirror data.
Attacks that exploit this kind of access
Add an official mirror queue entry to the regular MCP implementation queue. This creates a draft MCP implementation from the mirror data. This is an async operation. This action: 1. Creates a new draft MCP implementation using the mirror. It is categorised as a Write tool in the Langfuse Observability MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Langfuse Observability MCP server in PolicyLayer and add a rule for add_official_mirror_to_regular_queue: 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 Observability. Nothing to install.
add_official_mirror_to_regular_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_official_mirror_to_regular_queue 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 add_official_mirror_to_regular_queue. 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.
add_official_mirror_to_regular_queue is provided by the Langfuse Observability MCP server (langfuse-observability-mcp-server). 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 →