建立 Work Item 父子關聯(將 childId 設定 parentId 為父項)
AI agents use link_parent_work_item to create or update resources in Azure Devops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure Devops environment.
This tool creates a parent-child relationship between two work items in Azure DevOps. It modifies existing work item data by setting a hierarchical link, which is a reversible write operation. It does not delete data or execute code, making Write the most appropriate category. Misuse could reorganize work item hierarchies incorrectly, but the blast radius is limited to project structure.
From the tool's definition 建立 Work Item 父子關聯(將 childId 設定 parentId 為父項)— 'establishes parent-child relationship', i.e., creates/modifies a link between work items
Attacks that exploit this kind of access
建立 Work Item 父子關聯(將 childId 設定 parentId 為父項). It is categorised as a Write tool in the Azure Devops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure Devops MCP server in PolicyLayer and add a rule for link_parent_work_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 Azure Devops. Nothing to install.
link_parent_work_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 link_parent_work_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 link_parent_work_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.
link_parent_work_item is provided by the Azure Devops MCP server (wuhuangjia/azure-devops-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 →