AI agents use create-work-item to create or update resources in DevOps Enhanced MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DevOps Enhanced MCP environment.
Creating a work item adds data to Azure DevOps but is not destructive (it can be deleted or modified) and does not execute arbitrary code or move financial resources. It modifies the project state by introducing new work tracking items, making it a Write action.
From the tool's definition The tool name and description indicate it 'Create a new work item in Azure DevOps', which creates new data within the system. This is a reversible write operation.
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 DevOps Enhanced MCP, 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 in Azure DevOps. It is categorised as a Write tool in the DevOps Enhanced MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DevOps Enhanced 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 DevOps Enhanced MCP. 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 DevOps Enhanced MCP server (wangkanai/devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DevOps Enhanced MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 DevOps Enhanced MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.