stop_build · Jenkins MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_build does on Jenkins MCP Server

AI agents invoke stop_build to trigger actions in Jenkins MCP Server. 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 stop_build needs a policy

While stopping a build does not permanently delete data (which would be Destructive), it actively interrupts a running CI/CD pipeline execution. This is a form of external operation execution that modifies the state of infrastructure. The severity is high because misuse could disrupt production deployments, testing pipelines, or critical builds, potentially causing operational impact and delays.

From the tool's definition The tool 'stop_build' performs an action on a running Jenkins build by job name and build number. The description states it will 'Stop / abort a running Jenkins build,' which is an active operation that interrupts an external process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_build Rate-limited

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": {
    "stop_build": {
      "limits": [
        {
          "counter": "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 MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_build

What does the stop_build tool do? +

Stop / abort a running Jenkins build by job name and build number. It is categorised as a Execute tool in the Jenkins MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_build? +

Register the Jenkins MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.

What risk level is stop_build? +

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

Can I rate-limit stop_build? +

Yes. Add a rate_limit block to the 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 stop_build completely? +

Set action: deny in the PolicyLayer policy for 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 stop_build? +

stop_build is provided by the Jenkins MCP Server MCP server (mingtian6000/mcpservers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.