consultar_cnes
AI agents call consultar_cnes 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.
This is a read-only query tool that retrieves healthcare facility or professional registry information from CNES. It has no side effects, does not modify data, and does not execute arbitrary operations. The lack of a description slightly reduces confidence, but context from sibling tools and the server's stated purpose (querying Brazilian healthcare data) supports classification as Read with low severity.
From the tool's definition Tool name 'consultar_cnes' suggests querying CNES (Cadastro Nacional de Estabelecimentos de Saúde — Brazilian national health facility registry). The server description indicates this tool retrieves data from CNES.
Attacks that exploit this kind of access
consultar_cnes. 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 consultar_cnes: 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.
consultar_cnes 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 consultar_cnes 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 consultar_cnes. 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.
consultar_cnes 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 →