Create a comment on a pull request
AI agents use azure_devops_create_pr_comment to create or update resources in Cursor Azure Devops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cursor Azure Devops environment.
This tool creates new comments on pull requests, which is a reversible write operation. Comments can be edited or deleted, making it Write rather than Destructive. The blast radius is medium because an AI agent could spam comments, post misleading information, or disrupt collaboration workflows, but the effects are not permanent and do not directly delete data or execute arbitrary code.
From the tool's definition Tool name includes 'create' and description states 'Create a comment on a pull request', indicating creation of new data (comments) in Azure DevOps.
Documented attack patterns abuse exactly the kind of access azure_devops_create_pr_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cursor Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for azure_devops_create_pr_comment:
{
"version": "1",
"default": "deny",
"tools": {
"azure_devops_create_pr_comment": {
"limits": [
{
"counter": "azure_devops_create_pr_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} azure_devops_create_pr_comment 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 comment on a pull request. It is categorised as a Write tool in the Cursor Azure Devops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cursor Azure Devops MCP server in PolicyLayer and add a rule for azure_devops_create_pr_comment: 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 Cursor Azure Devops. Nothing to install.
azure_devops_create_pr_comment 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 azure_devops_create_pr_comment 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 azure_devops_create_pr_comment. 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.
azure_devops_create_pr_comment is provided by the Cursor Azure Devops MCP server (maximtitovich/cursor-azure-devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cursor Azure Devops, 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.
20 Cursor Azure Devops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.