jenkins_quiet_down · Mcp Jenkins MCP: Risk & Policy

WHAT IT DOES

What jenkins_quiet_down does on Mcp Jenkins

AI agents invoke jenkins_quiet_down to trigger actions in Mcp Jenkins. 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_quiet_down needs a policy

This tool triggers an operational mode change in Jenkins that prevents new builds from starting. While not destructive (it's reversible via jenkins_cancel_quiet_down), and not a direct code execution, it executes a command that changes system behavior and affects dependent processes. The blast radius is high: stopping all builds in Jenkins can disrupt CI/CD pipelines, block deployments, and impact teams.

From the tool's definition Tool description states it will 'Put Jenkins into quiet mode — no new builds will start' which is an operational state change that halts job execution pipeline. This is an external system state modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jenkins_quiet_down Rate-limited

jenkins_quiet_down 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_quiet_down": {
      "limits": [
        {
          "counter": "jenkins_quiet_down_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 Mcp Jenkins, so you can run agents against it safely.

FAQ

Questions about jenkins_quiet_down

What does the jenkins_quiet_down tool do? +

Put Jenkins into quiet mode — no new builds will start until cancelled (requires confirm: true). It is categorised as a Execute tool in the Mcp Jenkins 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_quiet_down? +

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

What risk level is jenkins_quiet_down? +

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

Can I rate-limit jenkins_quiet_down? +

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

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

jenkins_quiet_down is provided by the Mcp Jenkins MCP server (@kud/mcp-jenkins). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.