Compute health (log volume, error %, fatal count, p99 latency, status) for one service over a window.
AI agents call get_service_health to retrieve information from LogSentry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a monitoring/observability read operation. It retrieves and calculates statistics from existing logs to assess service health, analogous to a GET request or database query. There are no side effects on the monitored system, no code execution, no data modification, and no destructive or financial implications.
From the tool's definition The tool computes and retrieves health metrics (log volume, error %, fatal count, p99 latency, status) for a service—it queries and reports existing data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Compute health (log volume, error %, fatal count, p99 latency, status) for one service over a window. It is categorised as a Read tool in the LogSentry MCP MCP Server, which means it retrieves data without modifying state.
Register the LogSentry MCP server in PolicyLayer and add a rule for get_service_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 LogSentry MCP. Nothing to install.
get_service_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_service_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_service_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_service_health is provided by the LogSentry MCP server (mehtaniravm/logsentrymcpgooglehangout). 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 →