create_or_update_job_from_jenkinsfile
AI agents use create_or_update_job_from_jenkinsfile to create or update resources in Jenkins MCP Tool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jenkins MCP Tool environment.
This tool creates or updates Jenkins job definitions, which are reversible Write operations. While misuse could trigger unintended builds or modify CI/CD pipelines (affecting production deployments), it does not irreversibly delete data (would be Destructive) or execute arbitrary code execution beyond job definition (would be Execute).
From the tool's definition Tool name 'create_or_update_job_from_jenkinsfile' directly indicates creation or modification of Jenkins jobs via Jenkinsfile. The verb 'create_or_update' is inherently reversible Write operation.
Attacks that exploit this kind of access
create_or_update_job_from_jenkinsfile. It is categorised as a Write tool in the Jenkins MCP Tool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jenkins MCP Tool MCP server in PolicyLayer and add a rule for create_or_update_job_from_jenkinsfile: 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 MCP Tool. Nothing to install.
create_or_update_job_from_jenkinsfile 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 create_or_update_job_from_jenkinsfile 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 create_or_update_job_from_jenkinsfile. 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.
create_or_update_job_from_jenkinsfile is provided by the Jenkins MCP Tool MCP server (xhuaustc/jenkins-mcp). 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 →