Unlink an official mirror queue entry from its linked MCP server. This is a synchronous operation. This action: 1. Removes the mcp_server_id from all mirrors in this queue entry 2. Resets the queue entry status to pending (pending_new or pending_update based on history) 3. The previously linked s...
AI agents use unlink_official_mirror_queue_item 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 modifies a queue entry by removing a server linkage and resetting its status to pending. This is a reversible write operation — the previously linked server is not modified, and the queue entry can be re-processed. No data is permanently deleted, no code is executed, and no financial transaction occurs. The most severe applicable category is Write.
From the tool's definition Removes the mcp_server_id from all mirrors in this queue entry, Resets the queue entry status to pending — modifies data reversibly (entry can be re-linked, status is reset not deleted)
Attacks that exploit this kind of access
Unlink an official mirror queue entry from its linked MCP server. This is a synchronous operation. This action: 1. Removes the mcp_server_id from all mirrors in this queue entry 2. Resets the queue entry status to pending (pending_new or pending_update based on history) 3. The previously linked server is not modified Use cases: - Correct a mistaken server linkage - Re-process a queue entry with a different server - Reset an entry for re-evaluation - Unlink before linking to a different server Note: After unlinking, the queue entry will return to pending status and can be: - Approved again with a different server (approve_official_mirror_queue_item) - Added to the regular queue as a new draft (add_official_mirror_to_regular_queue) - Rejected (reject_official_mirror_queue_item). 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 unlink_official_mirror_queue_item: 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.
unlink_official_mirror_queue_item 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 unlink_official_mirror_queue_item 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 unlink_official_mirror_queue_item. 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.
unlink_official_mirror_queue_item 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.
unlink_official_mirror_queue_item is one line of Langfuse Observability's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →