Request cancellation of a running workspace bundle operation.
AI agents invoke jenkins_cancel_workspace_bundle_download to trigger actions in Jenkins Http. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (cancelling a running process) on the Jenkins server. It does not merely read data, nor does it irreversibly delete/overwrite data — it interrupts an in-progress bundle download/operation. This maps to Execute, as it triggers an external operation whose effects depend on runtime state.
From the tool's definition Request cancellation of a running workspace bundle operation
Attacks that exploit this kind of access
Request cancellation of a running workspace bundle operation. It is categorised as a Execute tool in the Jenkins Http MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_cancel_workspace_bundle_download: 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_workspace_bundle_download is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jenkins_cancel_workspace_bundle_download 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_workspace_bundle_download. 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_workspace_bundle_download 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 →