create_work_item
A write tool on the Azure DevOps MCP server.
This record as markdown: /tools/abdelrhmansror-azuredevopsmcp/create-work-item.md
What create_work_item does on Azure DevOps MCP Server
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.
Why create_work_item is rated Medium
Creating work items (backlog items, bugs, tasks) in Azure DevOps is a reversible modification of project data. This is Write-category because items can be edited or deleted by subsequent actions.
From the tool's definition Tool name is 'create_work_item' and sibling tools include 'create_bug' and 'create_product_backlog_item', indicating this tool creates new items in Azure DevOps work tracking. The description is empty, limiting precision.
Attacks that exploit this kind of access
The rule that runs create_work_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Azure DevOps MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_work_item, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Azure DevOps MCP Server, apply this rule, and every create_work_item call is checked against it from then on.
Questions about create_work_item
create_work_item is a write tool on the Azure DevOps MCP Server MCP server. 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 (abdelrhmansror/azuredevopsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Azure DevOps MCP Server, and thousands of servers like it.
This server
Across the catalogue