run_groovy_script · Mcp Jenkins MCP: Risk & Policy

WHAT IT DOES

What run_groovy_script does on Mcp Jenkins

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

Groovy scripts in Jenkins execute arbitrary code on Jenkins servers, potentially with access to Jenkins internals, file systems, and environment variables. This is a classic Execute-category capability with critical severity due to unrestricted code execution potential. No constraints on script content are documented, making this a high-impact vector if an AI agent is misused or prompt-injected.

From the tool's definition Tool name 'run_groovy_script' indicates execution of arbitrary Groovy code, which is a full programming language capable of system commands. Description is empty, but the name alone indicates code execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_groovy_script Rate-limited

run_groovy_script 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": {
    "run_groovy_script": {
      "limits": [
        {
          "counter": "run_groovy_script_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 run_groovy_script

What does the run_groovy_script tool do? +

run_groovy_script. 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 run_groovy_script? +

Register the Mcp Jenkins MCP server in PolicyLayer and add a rule for run_groovy_script: 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 run_groovy_script? +

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

Can I rate-limit run_groovy_script? +

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

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

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