Cancel a Jenkins queue item. Requires JENKINS_MCP_ENABLE_WRITES=1.
AI agents call jenkins_cancel_queue_item to permanently remove resources in Jenkins Http — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a queue item irreversibly removes it from the Jenkins build queue. Once cancelled, that queued build is gone and cannot be recovered or re-queued automatically, making this a destructive action. The requirement of JENKINS_MCP_ENABLE_WRITES=1 confirms it mutates server state. High severity because misuse could cancel critical CI/CD builds silently.
From the tool's definition Cancel a Jenkins queue item
Attacks that exploit this kind of access
Cancel a Jenkins queue item. Requires JENKINS_MCP_ENABLE_WRITES=1. It is categorised as a Destructive tool in the Jenkins Http MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_cancel_queue_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 Jenkins Http. Nothing to install.
jenkins_cancel_queue_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the jenkins_cancel_queue_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 jenkins_cancel_queue_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.
jenkins_cancel_queue_item is provided by the Jenkins Http MCP server (mdtahmidhossain/jenkins-http-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →