Fetch the latest tickets with pagination support
AI agents call get_tickets to retrieve information from Zendesk MCP Server 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 data without creating, modifying, or deleting content. It is a straightforward data retrieval operation with no side effects, making it a Read category risk. Severity is low because unauthorized ticket viewing, while a confidentiality concern, does not directly enable harmful actions like data destruction, financial transactions, or code execution.
From the tool's definition Tool description states 'Fetch the latest tickets with pagination support' - a retrieval operation with no modification or deletion capabilities. The verb 'Fetch' and context of pagination indicate query/read access only.
Attacks that exploit this kind of access
Fetch the latest tickets with pagination support. It is categorised as a Read tool in the Zendesk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zendesk MCP Server MCP server in PolicyLayer and add a rule for get_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 Zendesk MCP Server. Nothing to install.
get_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 get_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 get_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.
get_tickets is provided by the Zendesk MCP Server MCP server (kdopenshaw/zendesk-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 →