zendesk_list_tickets
AI agents call zendesk_list_tickets to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' operation is a standard read-only query that retrieves data from Zendesk without side effects. Even though the description is empty, the tool name and context from similar list operations on the same server strongly indicate this is a data retrieval tool. Confidence is high because 'list' operations across MCP servers consistently map to read-only queries.
From the tool's definition Tool name 'zendesk_list_tickets' indicates a listing/retrieval operation. The 'list' verb and 'tickets' object clearly suggest querying existing data without modification.
Attacks that exploit this kind of access
zendesk_list_tickets. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for zendesk_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 Integrations MCP. Nothing to install.
zendesk_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 zendesk_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 zendesk_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.
zendesk_list_tickets is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →