jenkins_update_job_config · Jenkins Http MCP: Risk & Policy

WHAT IT DOES

What jenkins_update_job_config does on Jenkins Http

AI agents use jenkins_update_job_config to create or update resources in Jenkins Http — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jenkins Http environment.

WHY IT NEEDS A POLICY

Why jenkins_update_job_config needs a policy

This tool creates or modifies job configuration data reversibly via the config.xml file replacement. While it can significantly impact Jenkins job behavior (build scripts, parameters, triggers, etc.), the changes are not inherently destructive—configurations can be reverted or restored.

From the tool's definition Tool description states 'Replace job config.xml', which modifies the job configuration file. The requirement for 'write and job-config flags' confirms this is a write operation with intentional access controls.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jenkins_update_job_config Rate-limited

jenkins_update_job_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_update_job_config": {
      "limits": [
        {
          "counter": "jenkins_update_job_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_update_job_config

What does the jenkins_update_job_config tool do? +

Replace job config.xml. Requires write and job-config flags. It is categorised as a Write tool in the Jenkins Http MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on jenkins_update_job_config? +

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

jenkins_update_job_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jenkins_update_job_config? +

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

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

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