Critical Risk →

mcp_ado_wit_work_item_unlink

Remove links from a work item

Permanently breaks work item relationships

Part of the Azure DevOps MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@@azure-devops/mcp Destructive Risk 4/5

AI agents may call mcp_ado_wit_work_item_unlink to permanently remove or destroy resources in Azure DevOps. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call mcp_ado_wit_work_item_unlink in a loop, permanently destroying resources in Azure DevOps. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

azure-devops.yaml
tools:
  mcp_ado_wit_work_item_unlink:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Azure DevOps policy for all 84 tools.

Tool Name mcp_ado_wit_work_item_unlink
Category Destructive
Risk Level Critical

View all 84 tools →

Agents calling destructive-class tools like mcp_ado_wit_work_item_unlink have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

mcp_ado_wit_work_item_unlink is one of the critical-risk operations in Azure DevOps. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the mcp_ado_wit_work_item_unlink tool do? +

Remove links from a work item. It is categorised as a Destructive tool in the Azure DevOps MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mcp_ado_wit_work_item_unlink? +

Add a rule in your Intercept YAML policy under the tools section for mcp_ado_wit_work_item_unlink. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Azure DevOps MCP server.

What risk level is mcp_ado_wit_work_item_unlink? +

mcp_ado_wit_work_item_unlink is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mcp_ado_wit_work_item_unlink? +

Yes. Add a rate_limit block to the mcp_ado_wit_work_item_unlink rule in your Intercept 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.

How do I block mcp_ado_wit_work_item_unlink completely? +

Set action: deny in the Intercept policy for mcp_ado_wit_work_item_unlink. 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.

What MCP server provides mcp_ado_wit_work_item_unlink? +

mcp_ado_wit_work_item_unlink is provided by the Azure DevOps MCP server (@@azure-devops/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Azure DevOps

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.