Health check endpoint for container monitoring and status verification
AI agents call health_check to retrieve information from Prometheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the health/status of a container or service. It retrieves monitoring data for verification purposes with no side effects, modifications, or state changes. This is a classic Read operation. The low severity reflects minimal blast radius—a malicious agent could only gather information about system health status, not affect metrics, data, or infrastructure.
From the tool's definition Tool name is 'health_check' and description states 'Health check endpoint for container monitoring and status verification'. Health checks retrieve status information without modifying any data.
Attacks that exploit this kind of access
Health check endpoint for container monitoring and status verification. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for health_check: 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 Prometheus MCP Server. Nothing to install.
health_check 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 health_check 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 health_check. 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.
health_check is provided by the Prometheus MCP Server MCP server (raihan0824/prometheus-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 →