Create a work item on the board. type options: Task, Bug, User Story, Epic, Feature.
AI agents use create_work_item to create or update resources in Az Devops Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Az Devops Cli environment.
This tool creates new data structures (work items) in Azure DevOps but does not delete, execute arbitrary code, or move money. Creation is reversible (items can be deleted later). The blast radius is medium because a compromised agent could flood the board with spam work items, clutter project tracking, or create misleading task assignments, but this does not cause irreversible harm or financial impact.
From the tool's definition Tool description explicitly states 'Create a work item on the board' — a reversible creation action that modifies project management data.
Attacks that exploit this kind of access
Create a work item on the board. type options: Task, Bug, User Story, Epic, Feature. It is categorised as a Write tool in the Az Devops Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Az Devops Cli MCP server in PolicyLayer and add a rule for create_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 Az Devops Cli. Nothing to install.
create_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 create_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 create_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.
create_work_item 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 →