Get detailed information about a specific pull request. Returns complete PR data including title, description, status, reviewers, work items, commits, policy evaluations, and merge status. Useful for getting the full context of a PR. Response includes all associated metadata.
AI agents call azure_devops_pull_request_by_id to retrieve information from Cursor Azure Devops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries pull request information from Azure DevOps. It has no side effects—it does not create, modify, delete, or execute any operations. The returned data includes PR metadata (title, description, status, reviewers, etc.) but accessing this information causes no changes to the system. This is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name includes 'get' semantic (azure_devops_pull_request_by_id), description states 'Get detailed information about a specific pull request' and 'Returns complete PR data'. Explicitly retrieves metadata without modification.
Documented attack patterns abuse exactly the kind of access azure_devops_pull_request_by_id 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_pull_request_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"azure_devops_pull_request_by_id": {}
}
}azure_devops_pull_request_by_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific pull request. Returns complete PR data including title, description, status, reviewers, work items, commits, policy evaluations, and merge status. Useful for getting the full context of a PR. Response includes all associated metadata. It is categorised as a Read tool in the Cursor Azure Devops MCP Server, which means it retrieves data without modifying state.
Register the Cursor Azure Devops MCP server in PolicyLayer and add a rule for azure_devops_pull_request_by_id: 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_pull_request_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the azure_devops_pull_request_by_id 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_pull_request_by_id. 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_pull_request_by_id 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.