Delete a job. Requires write, job-config, and delete flags.
AI agents call jenkins_delete_job 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.
The tool performs an irreversible deletion operation on Jenkins jobs. This is classified as Destructive rather than Write because deletion cannot be undone—the job configuration, history, and metadata are permanently removed. The severity is high because an agent misusing this tool could delete critical CI/CD jobs, disrupting builds and deployments.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a job.' This is an irreversible operation that removes job configurations and associated data.
Attacks that exploit this kind of access
Delete a job. Requires write, job-config, and delete flags. 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_delete_job: 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_delete_job 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_delete_job 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_delete_job. 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_delete_job 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 →