Get Jenkins build log.
AI agents call get_build_log to retrieve information from Jenkins MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves build log data from Jenkins without creating, modifying, deleting, or executing anything. It is a read-only query operation with no side effects. The low severity reflects that accessing build logs, while potentially sensitive depending on content, does not directly harm systems or data integrity.
From the tool's definition Tool name is 'get_build_log' and description states 'Get Jenkins build log.' The verb 'Get' and lack of any modification or side-effect language clearly indicate a retrieval operation.
Attacks that exploit this kind of access
Get Jenkins build log. It is categorised as a Read tool in the Jenkins MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP Tool MCP server in PolicyLayer and add a rule for get_build_log: 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 Tool. Nothing to install.
get_build_log 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_log 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_log. 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_log is provided by the Jenkins MCP Tool MCP server (xhuaustc/jenkins-mcp). 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 →