AI agents call health_check to retrieve information from Scorton without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health checks are monitoring operations that query system state and return status information. They do not create, modify, delete data, execute external code, or commit financial obligations. The tool is purely observational and diagnostic in nature, making it a Read category risk with low severity due to minimal blast radius if misused (only information disclosure of operational status).
From the tool's definition Tool name 'health_check' and description 'Operational health check for monitoring integrations' indicate a read-only status check that retrieves system health metrics without modifying or executing external operations.
Attacks that exploit this kind of access
Operational health check for monitoring integrations. It is categorised as a Read tool in the Scorton MCP Server, which means it retrieves data without modifying state.
Register the Scorton 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 Scorton. 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 Scorton MCP server (yojedesign/scorton-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 →