AI agents call list_builds to retrieve information from Jenkins without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical build metadata (results, timestamps, durations) from a Jenkins job without modifying, executing, or deleting any data. It is a pure read operation with minimal blast radius—an AI agent could at most enumerate build history, which does not compromise Jenkins controller integrity or trigger unintended actions.
From the tool's definition Tool description states 'Return up to ``limit`` recent builds for ``job_name`` with result/timestamp/duration' — a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Return up to limit recent builds for job_name with result/timestamp/duration. It is categorised as a Read tool in the Jenkins MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP server in PolicyLayer and add a rule for list_builds: 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. Nothing to install.
list_builds is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_builds 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 list_builds. 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.
list_builds is provided by the Jenkins MCP server (lokimcpuniverse/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 →