monitor_server_health
AI agents call monitor_server_health to retrieve information from Observability MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health monitoring tools retrieve system status and metrics without modifying infrastructure, executing code, or triggering side effects. This is a classic Read category function: querying the state of a system for diagnostic purposes. Low severity because misuse would only expose observability data, not compromise systems or data integrity.
From the tool's definition Tool name 'monitor_server_health' and server context indicate passive health monitoring. Server description emphasizes 'real-time health checks' and 'monitoring' without mentioning modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
monitor_server_health. It is categorised as a Read tool in the Observability MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Observability MCP Server MCP server in PolicyLayer and add a rule for monitor_server_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 Observability MCP Server. Nothing to install.
monitor_server_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 monitor_server_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 monitor_server_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.
monitor_server_health is provided by the Observability MCP Server MCP server (sandraschi/observability-mcp). 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 →