Atualiza um centro de custo. Campo 'id' obrigatório.
AI agents use rhid_atualizar_centro_custo to create or update resources in RHID MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RHID MCP Server environment.
This tool updates (modifies) an existing cost center record in the system. This is a reversible write operation — the record can be updated again. No deletion or financial transaction is involved. Severity is medium because cost center data affects financial reporting and employee attribution, but misuse is recoverable.
From the tool's definition 'Atualiza um centro de custo' — updates a cost center record; 'Campo id obrigatório' confirms it modifies an existing entity by ID
Attacks that exploit this kind of access
Atualiza um centro de custo. Campo 'id' obrigatório. It is categorised as a Write tool in the RHID MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RHID MCP Server MCP server in PolicyLayer and add a rule for rhid_atualizar_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_atualizar_centro_custo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rhid_atualizar_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_atualizar_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_atualizar_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 →