Copy/duplicate a Jenkins job under a new name
AI agents use jenkins_copy_job to create or update resources in Mcp Jenkins — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Jenkins environment.
This tool creates a new job configuration by copying an existing one. While it does not delete data (which would be Destructive), it does irreversibly create new job configurations that persist in Jenkins. The severity is high because an agent could duplicate sensitive, privileged, or malicious jobs at scale, potentially compromising CI/CD pipelines.
From the tool's definition Tool name is "jenkins_copy_job" and description states it will "Copy/duplicate a Jenkins job under a new name". This is a create/duplicate operation that modifies the Jenkins configuration state.
Attacks that exploit this kind of access
Copy/duplicate a Jenkins job under a new name. It is categorised as a Write tool in the Mcp Jenkins MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Jenkins MCP server in PolicyLayer and add a rule for jenkins_copy_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 Mcp Jenkins. Nothing to install.
jenkins_copy_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_copy_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_copy_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_copy_job 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.
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 →