Cria um centro de custo.
AI agents use criar_centro_custo to create or update resources in MCP Officegest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Officegest environment.
This tool creates a new cost center record in the Officegest system, which is a reversible write operation. While it modifies the database by adding a new entity, cost center creation is typically not destructive and does not involve financial transactions directly (unlike tools that would move money or create payment obligations).
From the tool's definition Tool name 'criar_centro_custo' translates to 'create cost center'. Description states 'Cria um centro de custo' ('Creates a cost center'). The verb 'criar' (create) and the tool's function of creating a new entity indicates data modification.
Attacks that exploit this kind of access
Cria um centro de custo. It is categorised as a Write tool in the MCP Officegest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for criar_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 MCP Officegest. Nothing to install.
criar_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 criar_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 criar_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.
criar_centro_custo is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-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 →