AI agents use create_work_item 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 creates new data in Azure DevOps (work items such as user stories, tasks, bugs). Creation is a reversible Write operation—the artifact can be modified or deleted later. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external systems directly. The blast radius is limited to the Azure DevOps project scope.
From the tool's definition Tool name: 'create_work_item'; description: 'Create a new work item'. The verb 'Create' indicates data creation; work items in Azure DevOps are reversibly modifiable objects (can be edited, deleted, or closed).
Documented attack patterns abuse exactly the kind of access create_work_item 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 create_work_item:
{
"version": "1",
"default": "deny",
"tools": {
"create_work_item": {
"limits": [
{
"counter": "create_work_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_work_item 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.
Create a new work item. 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 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 Azure DevOps MCP Server. 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 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.