list_tickets
AI agents call list_tickets to retrieve information from Gorgias MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_tickets' tool retrieves or queries ticket data with no side effects. While the description is empty, the naming pattern and context of sibling tools strongly indicate this is a read operation that returns a list of tickets without modifying data. No code execution, deletions, or financial transactions are involved.
From the tool's definition Tool name is 'list_tickets' which follows the read/retrieve pattern (list, get, fetch). Sibling tools include 'get_customer', 'get_ticket', and 'list_customers' which are clearly read operations. Server is a helpdesk API for querying and managing tickets.
Attacks that exploit this kind of access
list_tickets. It is categorised as a Read tool in the Gorgias MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gorgias MCP Server MCP server in PolicyLayer and add a rule for list_tickets: 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.
list_tickets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_tickets 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 list_tickets. 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.
list_tickets 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 →