criar_ticket
AI agents use criar_ticket 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.
The tool creates a new ticket (likely a support, sales, or operational ticket in the Officegest system). This is reversible (tickets can be updated or deleted), so it falls under Write rather than Destructive. Without a description, confidence is reduced, but the name and server context suggest data creation.
From the tool's definition Tool name 'criar_ticket' means 'create ticket' in Portuguese. The server manages clients, sales, and stock via CRUD operations. Creating a ticket typically generates a new record in a system, which is a write operation.
Attacks that exploit this kind of access
criar_ticket. 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_ticket: 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_ticket 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_ticket 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_ticket. 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_ticket 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 →