criar_documento_venda
AI agents use criar_documento_venda 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 sales documents, which is a reversible write operation that modifies data in the system. It does not delete data (would be Destructive) or move money directly (would be Financial), though sales documents may have downstream financial implications. Medium severity reflects potential business process impact if documents are created incorrectly or maliciously, but the operation itself is reversible.
From the tool's definition Tool name 'criar_documento_venda' translates to 'create_sales_document'. The prefix 'criar_' (create) and context within a sales/inventory management API indicate data creation. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
criar_documento_venda. 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_documento_venda: 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_documento_venda 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_documento_venda 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_documento_venda. 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_documento_venda 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 →