Verifica a saude de todos os subsistemas do servidor MCP.
AI agents call health_check to retrieve information from Manual RAG — SIH/SUS Query System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health checks are read-only operations that retrieve status information about system components. They have no side effects, do not execute code or commands, do not modify data, and do not create financial obligations. The blast radius of misuse is minimal—an attacker could only learn about system status. This is a standard administrative monitoring tool.
From the tool's definition Tool name 'health_check' and description 'Verifica a saude de todos os subsistemas do servidor MCP' (Verifies the health of all MCP server subsystems).
Attacks that exploit this kind of access
Verifica a saude de todos os subsistemas do servidor MCP. It is categorised as a Read tool in the Manual RAG — SIH/SUS Query System MCP Server, which means it retrieves data without modifying state.
Register the Manual RAG — SIH/SUS Query System 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 Manual RAG — SIH/SUS Query System. 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 Manual RAG — SIH/SUS Query System MCP server (leonardo-amaral-3/mcp-datasus). 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 →