Rename a Jenkins job
AI agents use jenkins_rename_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 modifies existing Jenkins job state (the job name) reversibly. It does not execute builds, delete jobs, or trigger financial transactions. Among the sibling tools, jenkins_delete_job and jenkins_delete_build are Destructive, while jenkins_rename_job is only Write.
From the tool's definition Tool name 'jenkins_rename_job' and description 'Rename a Jenkins job' indicate modification of job metadata. Renaming is a reversible operation that changes job configuration without executing pipelines or deleting resources.
Attacks that exploit this kind of access
Rename a Jenkins job. 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_rename_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_rename_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_rename_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_rename_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_rename_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 →