criar_vendedor
AI agents use criar_vendedor 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.
Creating a seller record is a reversible data modification operation that affects business configuration but does not execute code, delete data, or move money. It fits the Write category. Severity is medium because unauthorized seller creation could distort sales records and reporting, but the impact is limited compared to financial or destructive operations.
From the tool's definition Tool name 'criar_vendedor' translates to 'create_seller' in Portuguese. The pattern matches other write operations on this server (e.g., 'adicionar_' prefix for adding, 'atualizar_' for updating). Tool description is empty, limiting specificity.
Attacks that exploit this kind of access
criar_vendedor. 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_vendedor: 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_vendedor 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_vendedor 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_vendedor. 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_vendedor 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 →