Get health information for a Jenkins job
AI agents call get_job_health 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 health status data about a Jenkins job without modifying state, executing builds, or triggering operations. It is a pure information retrieval operation analogous to other 'get_*' tools on the server (get_build_status, get_job_status, etc.).
From the tool's definition Tool name 'get_job_health' and description 'Get health information for a Jenkins job' indicate a retrieval operation. The verb 'Get' and lack of any modification, execution, or side-effect language confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access get_job_health gives an agent:
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_job_health:
{
"version": "1",
"default": "deny",
"tools": {
"get_job_health": {}
}
}get_job_health 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 health information for a Jenkins job. 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_job_health: 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_job_health 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_job_health 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_job_health. 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_job_health 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.
Start from Jenkins, 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.
14 Jenkins tools catalogued and risk-classified — across an index of 43,000+ MCP servers.