Elimina una relación existente entre dos Work Items de Azure DevOps.
AI agents call ado_remove_work_item_link to permanently remove resources in Mcp Azure — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool removes/deletes an existing relationship between two Work Items. Deleting a link is an irreversible action (the relationship is gone unless manually re-created), placing it in the Destructive category. Severity is medium because it affects traceability and dependency tracking between work items, but does not delete the work items themselves.
From the tool's definition "Elimina una relación existente entre dos Work Items" — 'Elimina' means 'Deletes/Removes' in Spanish, indicating irreversible removal of a link relationship between work items.
Attacks that exploit this kind of access
Elimina una relación existente entre dos Work Items de Azure DevOps. It is categorised as a Destructive tool in the Mcp Azure MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Azure MCP server in PolicyLayer and add a rule for ado_remove_work_item_link: 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 Mcp Azure. Nothing to install.
ado_remove_work_item_link is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ado_remove_work_item_link 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 ado_remove_work_item_link. 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.
ado_remove_work_item_link is provided by the Mcp Azure MCP server (soulberto/mcp-azure). 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 →