AI agents call get_build_console_tail 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 console output from a completed build, a read-only operation that queries existing data. It has no side effects, does not execute code or commands, and does not modify or delete data. The severity is low because console logs typically contain non-sensitive build metadata, though in some CI/CD environments they could contain credentials or secrets (mitigated by Jenkins access controls).
From the tool's definition Tool name 'get_build_console_tail' and description 'Get the tail of a specific build console output' indicate retrieval of build log data without modification or execution.
Attacks that exploit this kind of access
Get the tail of a specific build console output. 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 get_build_console_tail: 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.
get_build_console_tail 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_console_tail 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_console_tail. 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_console_tail is provided by the Jenkins MCP server (mcpland/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 →