Remove um centro de custo pelo ID.
AI agents call rhid_remover_centro_custo to permanently remove resources in RHID MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a cost center record from the system by its identifier. Cost centers are core business entities used for financial tracking and reporting. Deletion cannot be undone and would impact financial records, reporting accuracy, and organizational structure. This constitutes an irreversible destructive action.
From the tool's definition Tool name contains 'remover' (Portuguese for 'remove') and description states 'Remove um centro de custo pelo ID' (Remove a cost center by ID). The verb 'remove' in the context of deleting a cost center by ID indicates irreversible deletion of data.
Attacks that exploit this kind of access
Remove um centro de custo pelo ID. It is categorised as a Destructive tool in the RHID MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RHID MCP Server MCP server in PolicyLayer and add a rule for rhid_remover_centro_custo: 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_remover_centro_custo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rhid_remover_centro_custo 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_remover_centro_custo. 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_remover_centro_custo 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 →