Get the test report of a specific build in Jenkins
AI agents call get_build_test_report 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/queries test report data from Jenkins without modifying, deleting, or executing anything. It is a read-only operation that fetches information about an existing build's test results. Consistent with sibling tools like 'get_build', 'get_all_items', and 'get_all_plugins' which are all Read category. No destructive, financial, or execution risk.
From the tool's definition Tool name 'get_build_test_report' and description 'Get the test report of a specific build in Jenkins' indicate a retrieval operation with no side effects. Returns existing test report data from a completed build.
Attacks that exploit this kind of access
Get the test report of a specific build in 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_test_report: 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_test_report 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_test_report 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_test_report. 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_test_report 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 →