Create a top-level job from config.xml. Requires write and job-config flags.
AI agents use jenkins_create_job 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.
This tool creates a new Jenkins job, which is a reversible modification of Jenkins configuration state. While it modifies the Jenkins system, the action is not destructive (jobs can be deleted) and does not execute builds or arbitrary code directly—it only creates the job definition.
From the tool's definition Tool name is 'jenkins_create_job' and description states 'Create a top-level job from config.xml. Requires write and job-config flags.' The verb 'Create' and explicit mention of 'write' flag indicate data creation.
Attacks that exploit this kind of access
Create a top-level job from 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.
Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_create_job: 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.
jenkins_create_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jenkins_create_job 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.
Set action: deny in the PolicyLayer policy for jenkins_create_job. 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.
jenkins_create_job 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →