leitos_listar_uti
AI agents call leitos_listar_uti to retrieve information from AutoPeças MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern 'listar_*' (list) in Portuguese indicates a retrieval operation with no side effects. Although the description is empty which reduces confidence slightly, the consistent naming convention with other sibling tools on this server and the read-only semantic of 'listar' (list/enumerate) strongly suggests this is a data retrieval tool. It queries ICU bed information without modifying state.
From the tool's definition Tool name 'leitos_listar_uti' suggests listing/retrieval operation (listar = list in Portuguese). The 'leitos' (beds) prefix indicates querying hospital bed/ICU data.
Attacks that exploit this kind of access
leitos_listar_uti. It is categorised as a Read tool in the AutoPeças MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AutoPeças MCP Server MCP server in PolicyLayer and add a rule for leitos_listar_uti: 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 AutoPeças MCP Server. Nothing to install.
leitos_listar_uti 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 leitos_listar_uti 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 leitos_listar_uti. 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.
leitos_listar_uti is provided by the AutoPeças MCP Server MCP server (joao-parana/mcp-alura). 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 →