Get all linked work items. Use after bulk linking to verify hierarchy.
AI agents call get_work_item_relations to retrieve information from Az Devops Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing relationship data between work items in Azure DevOps. It performs no mutations, executions, deletions, or financial operations. The primary purpose is to read and display linked work item information, making it a straightforward Read category tool with low risk.
From the tool's definition Tool is described as 'Get all linked work items' and 'Use after bulk linking to verify hierarchy' - the verb 'Get' and the verification use case indicate pure data retrieval with no modifications, side effects, or external operations triggered.
Attacks that exploit this kind of access
Get all linked work items. Use after bulk linking to verify hierarchy. It is categorised as a Read tool in the Az Devops Cli MCP Server, which means it retrieves data without modifying state.
Register the Az Devops Cli MCP server in PolicyLayer and add a rule for get_work_item_relations: 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 Az Devops Cli. Nothing to install.
get_work_item_relations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_work_item_relations 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 get_work_item_relations. 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.
get_work_item_relations is provided by the Az Devops Cli MCP server (praisesinkamba/az-devops-cli-mcp). 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 →