get_build_test_results

THE RISK

Low Risk

Why get_build_test_results needs a policy

This tool retrieves historical test result data from a completed build, analogous to other sibling Read tools like get_build_logs and get_build_history. It has no side effects, does not trigger actions, and does not modify Jenkins state. The blast radius of misuse is minimal—an agent could only access test data it is already authorized to see.

From the tool's definition Tool name 'get_build_test_results' and description 'Get test results for a specific build' indicate a retrieval operation with no modification or execution of any build processes.

Documented attack patterns abuse exactly the kind of access get_build_test_results gives an agent:

POLICY

How to control get_build_test_results

PolicyLayer is an MCP gateway — it sits between your AI agents and Jenkins, and nothing reaches the server without passing your rules. This is the rule we recommend for get_build_test_results:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_build_test_results": {}
  }
}

get_build_test_results is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Jenkins — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jenkins tools

Execute trigger_build Trigger a Jenkins build Read get_build_console_output Get build console output Read get_build_history Get build history for a job Read get_build_logs Get build logs for a specific build Read get_build_parameters Get parameters used in a specific build Read get_build_status Get build status Read get_job_config Get Jenkins job configuration in XML format Read get_job_health Get health information for a Jenkins job

All 14 Jenkins tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_build_test_results

What does the get_build_test_results tool do? +

Get test results for a specific build. It is categorised as a Read tool in the Jenkins MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_build_test_results? +

Register the Jenkins MCP server in PolicyLayer and add a rule for get_build_test_results: 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.

What risk level is get_build_test_results? +

get_build_test_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_build_test_results? +

Yes. Add a rate_limit block to the get_build_test_results 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.

How do I block get_build_test_results completely? +

Set action: deny in the PolicyLayer policy for get_build_test_results. 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.

What MCP server provides get_build_test_results? +

get_build_test_results is provided by the Jenkins MCP server (truxt-ai/jenkins-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jenkins tool call.

Start from Jenkins, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →