Disable a job. Requires JENKINS_MCP_ENABLE_WRITES=1.
AI agents use jenkins_disable_job to create or update resources in Jenkins Http — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jenkins Http environment.
Disabling a job modifies its configuration state reversibly—the job can be re-enabled later. This is a Write operation (not Destructive, as no data is deleted or permanently lost) with medium severity because disabling a critical job could disrupt CI/CD pipelines and deployments if an AI agent misuses it, but the action is reversible and does not delete data or commit financial obligations.
From the tool's definition Tool description states 'Disable a job' and requires JENKINS_MCP_ENABLE_WRITES=1, indicating a write operation that modifies job state.
Attacks that exploit this kind of access
Disable a job. Requires JENKINS_MCP_ENABLE_WRITES=1. It is categorised as a Write tool in the Jenkins Http MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_disable_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_disable_job 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 jenkins_disable_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_disable_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_disable_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 →