Update build display name and/or description
AI agents use updateBuild to create or update resources in Jenkins MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jenkins MCP Server environment.
The tool modifies build attributes (display name and description) but does not delete, execute code, move money, or trigger new build processes. It is a reversible write operation on build metadata. Severity is medium because unauthorized modification of build metadata could obscure audit trails or confuse CI/CD visibility, but the changes are not destructive and can be undone.
From the tool's definition Tool name 'updateBuild' combined with description 'Update build display name and/or description' indicates modification of existing build metadata. This is reversible (display names and descriptions can be changed again or reverted).
Attacks that exploit this kind of access
Update build display name and/or description. It is categorised as a Write tool in the Jenkins MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jenkins MCP Server MCP server in PolicyLayer and add a rule for updateBuild: 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 Server. Nothing to install.
updateBuild 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 updateBuild 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 updateBuild. 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.
updateBuild is provided by the Jenkins MCP Server MCP server (umishra1504/jenkins-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 →