create_bug
A write tool on the Azure DevOps MCP server.
This record as markdown: /tools/abdelrhmansror-azuredevopsmcp/create-bug.md
What create_bug does on Azure DevOps MCP Server
AI agents use create_bug 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_bug is rated Medium
Creating a bug work item in Azure DevOps is a write operation—it creates new data (a bug record) reversibly, as bugs can be deleted or modified later. It does not execute arbitrary code, delete irreversibly, or move money. Medium severity reflects that an agent could spam or create incorrect bug records, requiring cleanup, but the impact is bounded and reversible.
From the tool's definition Tool name is 'create_bug' and sibling tools include 'create_product_backlog_item' and 'create_work_item', which are clearly data creation operations in Azure DevOps.
Attacks that exploit this kind of access
The rule that runs create_bug 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_bug, this is the rule to start with:
create_bug 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_bug call is checked against it from then on.
Questions about create_bug
create_bug 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_bug: 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_bug 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_bug 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_bug. 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_bug 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