Return a small health snapshot from top-level Jenkins JSON and version headers.
AI agents call jenkins_health to retrieve information from Jenkins Http without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
jenkins_health retrieves system status information without modifying state, executing commands, or causing side effects. This is a passive monitoring/diagnostic operation that falls squarely into the Read category. The low severity reflects minimal blast radius—an AI misuse of this tool would only expose Jenkins metadata and health status, not trigger builds, delete data, or compromise security.
From the tool's definition Tool description states 'Return a small health snapshot from top-level Jenkins JSON and version headers.' The verb 'Return' and noun 'snapshot' indicate data retrieval only. No mutation, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Return a small health snapshot from top-level Jenkins JSON and version headers. It is categorised as a Read tool in the Jenkins Http MCP Server, which means it retrieves data without modifying state.
Register the Jenkins Http MCP server in PolicyLayer and add a rule for jenkins_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 Http. Nothing to install.
jenkins_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 jenkins_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 jenkins_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.
jenkins_health is provided by the Jenkins Http MCP server (mdtahmidhossain/jenkins-http-mcp-server). 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 →