get_last_builds
AI agents call get_last_builds to retrieve information from MCP Jenkins Server 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 information without modifying, executing, or deleting anything. It has no side effects and fits the Read category (retrieve or query data). While the description is empty, the naming convention and server context strongly suggest passive data retrieval.
From the tool's definition Tool name 'get_last_builds' and server context indicate retrieval of build history/metadata from Jenkins. Server description mentions 'view server info', 'inspect builds', and sibling tools like 'get_build_info' and 'get_build_console_output' confirm the Read…
Attacks that exploit this kind of access
get_last_builds. It is categorised as a Read tool in the MCP Jenkins Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Jenkins Server MCP server in PolicyLayer and add a rule for get_last_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 MCP Jenkins Server. Nothing to install.
get_last_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 get_last_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 get_last_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.
get_last_builds is provided by the MCP Jenkins Server MCP server (winjayx/014.jenkinsmcp). 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 →