Add or remove links between work items
AI agents use manage_work_item_link to create or update resources in Azure DevOps MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure DevOps MCP Server environment.
This tool modifies the relationships and links between work items in Azure DevOps. Adding links creates new metadata; removing links deletes those relationships. Both operations are reversible (links can be re-added) and do not irreversibly destroy work items, execute code, or trigger financial transactions. This places it in the Write category.
From the tool's definition Tool description states 'Add or remove links between work items' - both operations modify work item metadata reversibly.
Documented attack patterns abuse exactly the kind of access manage_work_item_link gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_work_item_link:
{
"version": "1",
"default": "deny",
"tools": {
"manage_work_item_link": {
"limits": [
{
"counter": "manage_work_item_link_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_work_item_link stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add or remove links between work items. It is categorised as a Write tool in the Azure DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for manage_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 Azure DevOps MCP Server. Nothing to install.
manage_work_item_link 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 manage_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 manage_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.
manage_work_item_link is provided by the Azure DevOps MCP Server MCP server (tiberriver256/mcp-server-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Azure DevOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Azure DevOps MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.