add_message_to_ticket
AI agents use add_message_to_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.
Adding a message to a ticket creates or appends new data to a helpdesk record, which is a reversible write operation. The blast radius is medium because malicious messages could disrupt customer support workflows, impersonate support staff, or expose sensitive information, but the action is not destructive, financial, or code-execution in nature.
From the tool's definition Tool name 'add_message_to_ticket' indicates creation of message content within an existing ticket; sibling tools include 'create_ticket' (Write), 'get_ticket' (Read), and 'list_tickets' (Read), positioning this as a modification operation.
Attacks that exploit this kind of access
add_message_to_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 add_message_to_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.
add_message_to_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 add_message_to_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 add_message_to_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.
add_message_to_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 →