create_ticket
AI agents use create_ticket to create or update resources in Gorgias MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gorgias MCP Server environment.
This tool creates new helpdesk tickets, which is a reversible write operation. It modifies the helpdesk database by adding a new record. Severity is medium because misuse could create spam tickets or false support requests, but the impact is limited to the helpdesk system and the action can be undone by deleting tickets.
From the tool's definition Tool name is 'create_ticket' which indicates creation of new data. Server context shows this is a helpdesk system managing tickets and customers. The tool creates a new ticket in the Gorgias helpdesk system.
Attacks that exploit this kind of access
create_ticket. It is categorised as a Write tool in the Gorgias MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gorgias MCP Server MCP server in PolicyLayer and add a rule for create_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 Gorgias MCP Server. Nothing to install.
create_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 create_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 create_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.
create_ticket is provided by the Gorgias MCP Server MCP server (mattcoatsworth/gorgias-mcp-server). 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 →