jenkins_trigger_build · Jenkins Http MCP: Risk & Policy

WHAT IT DOES

What jenkins_trigger_build does on Jenkins Http

AI agents invoke jenkins_trigger_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_trigger_build needs a policy

Triggering a Jenkins build executes code/pipelines on the Jenkins server, which may compile code, run tests, deploy applications, or execute arbitrary scripts. The effects are determined by what the triggered job does, making this an Execute risk. While it could have Destructive or Financial impacts depending on job configuration, the tool itself is fundamentally an execution trigger.

From the tool's definition Tool description states 'Trigger a non-parameterized job build' which initiates an external operation (a Jenkins build execution) whose effects depend on the job configuration and environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jenkins_trigger_build Rate-limited

jenkins_trigger_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_trigger_build": {
      "limits": [
        {
          "counter": "jenkins_trigger_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_trigger_build

What does the jenkins_trigger_build tool do? +

Trigger a non-parameterized job 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_trigger_build? +

Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_trigger_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_trigger_build? +

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

Can I rate-limit jenkins_trigger_build? +

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

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

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