Busca um cargo pelo ID.
AI agents call rhid_buscar_cargo to retrieve information from RHID MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single job position/role record by its ID. It performs a lookup with no side effects, placing it firmly in the Read category with low severity.
From the tool's definition Busca um cargo pelo ID — 'Busca' means 'search/fetch', indicating a read-only retrieval of a job role record by ID.
Attacks that exploit this kind of access
Busca um cargo pelo ID. It is categorised as a Read tool in the RHID MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RHID MCP Server MCP server in PolicyLayer and add a rule for rhid_buscar_cargo: 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 RHID MCP Server. Nothing to install.
rhid_buscar_cargo 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 rhid_buscar_cargo 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 rhid_buscar_cargo. 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.
rhid_buscar_cargo is provided by the RHID MCP Server MCP server (miranda-ale/rhdi-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 →