AI agents call get_ticket_context 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 retrieves existing ticket conversation history without side effects. It is used to gather information prior to taking other actions (drafting notes or replies), but the tool itself only reads data. No data is created, modified, deleted, or executed. This is a straightforward Read operation with minimal risk—misuse would only expose information the agent already has access to through list_open_tickets.
From the tool's definition Tool description states 'Fetch the entire conversation history' with no mention of modifying, deleting, or executing actions. The verb 'Fetch' and the purpose of reading 'full context' before other actions indicate pure data retrieval.
Attacks that exploit this kind of access
Fetch the entire conversation history of a specific ticket ID. Used after list_open_tickets to read full context before drafting an internal note or reply. 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 get_ticket_context: 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.
get_ticket_context 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 get_ticket_context 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 get_ticket_context. 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.
get_ticket_context 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 →