jenkins_stop_build · Jenkins Http MCP: Risk & Policy

WHAT IT DOES

What jenkins_stop_build does on Jenkins Http

AI agents invoke jenkins_stop_build 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.

WHY IT NEEDS A POLICY

Why jenkins_stop_build needs a policy

Stopping a running build is an Execute-category action: it triggers an external operation with side effects that depend on runtime arguments (the build identifier). While not destructive (the build can be restarted), it interrupts an ongoing process and affects system state in ways that cannot be undone instantly.

From the tool's definition Tool name is 'jenkins_stop_build' with description 'Stop a running build.' This action triggers an external operation (stopping a Jenkins build process) whose effects depend on which build is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jenkins_stop_build Rate-limited

jenkins_stop_build stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jenkins_stop_build": {
      "limits": [
        {
          "counter": "jenkins_stop_build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jenkins Http, so you can run agents against it safely.

FAQ

Questions about jenkins_stop_build

What does the jenkins_stop_build tool do? +

Stop a running build. Requires JENKINS_MCP_ENABLE_WRITES=1. 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.

How do I enforce a policy on jenkins_stop_build? +

Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_stop_build: 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.

What risk level is jenkins_stop_build? +

jenkins_stop_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jenkins_stop_build? +

Yes. Add a rate_limit block to the jenkins_stop_build 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.

How do I block jenkins_stop_build completely? +

Set action: deny in the PolicyLayer policy for jenkins_stop_build. 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.

What MCP server provides jenkins_stop_build? +

jenkins_stop_build 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.