AI agents call list_open_tickets to retrieve information from Gorgias without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves ticket data without creating, modifying, executing, deleting, or committing financial actions. It is a straightforward read operation that fetches existing support ticket information for review purposes. The blast radius of misuse is minimal—an agent could retrieve ticket data unnecessarily but cannot cause harm through this read-only action.
From the tool's definition Tool description states 'Retrieve unresolved support tickets' with no modification or side effects. It returns data ('Returns the top N tickets') ordered by recency.
Attacks that exploit this kind of access
Retrieve unresolved support tickets (status=open) to find customers needing help. Returns the top N tickets ordered by most-recent-update. It is categorised as a Read tool in the Gorgias MCP Server, which means it retrieves data without modifying state.
Register the Gorgias MCP server in PolicyLayer and add a rule for list_open_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. Nothing to install.
list_open_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_open_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_open_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_open_tickets is provided by the Gorgias MCP server (nobanks/gorgias-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 →