Get specific build info from Jenkins
AI agents call get_build to retrieve information from Mcp Jenkins without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves build metadata and information from Jenkins without modifying, deleting, or executing any operations. It is a read-only query operation similar to the other sibling read tools (get_build_artifact, get_build_artifact_url, get_all_items, etc.). The blast radius of misuse is minimal—an AI agent could only access existing build information, not modify Jenkins state or trigger actions.
From the tool's definition Tool name 'get_build' and description 'Get specific build info from Jenkins' indicate a retrieval operation with no side effects. The verb 'Get' and context of querying build information aligns with data retrieval.
Attacks that exploit this kind of access
Get specific build info from Jenkins. It is categorised as a Read tool in the Mcp Jenkins MCP Server, which means it retrieves data without modifying state.
Register the Mcp Jenkins MCP server in PolicyLayer and add a rule for get_build: 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.
get_build 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 get_build 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 get_build. 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.
get_build is provided by the Mcp Jenkins MCP server (lanbaoshen/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 →