AI agents call get_build_status to retrieve information from Jenkins MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves build status information with no side effects. It performs a read-only query of build metadata/state, consistent with the Read category (get, fetch). The low severity reflects minimal blast radius—querying build status cannot damage infrastructure, trigger unintended builds, or affect data integrity.
From the tool's definition Tool name 'get_build_status' and description 'Get build status' indicate a retrieval operation that queries the current state of a build without modifying or triggering any Jenkins operations.
Documented attack patterns abuse exactly the kind of access get_build_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jenkins MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_build_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_build_status": {}
}
}get_build_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get build status. It is categorised as a Read tool in the Jenkins MCP MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP server in PolicyLayer and add a rule for get_build_status: 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. Nothing to install.
get_build_status 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_status 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_status. 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_status is provided by the Jenkins MCP server (kjozsa/jenkins-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jenkins MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Jenkins MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.