Get full detail of a Zendesk ticket including its comments.
AI agents call zendesk_get_ticket 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.
This tool retrieves ticket information from Zendesk—a read-only operation with no side effects. The blast radius is minimal: an AI agent misusing this tool could only expose sensitive information already stored in accessible tickets, not modify systems or trigger external actions. Severity is low because the impact is limited to information disclosure without operational consequences.
From the tool's definition Tool name 'zendesk_get_ticket' and description 'Get full detail of a Zendesk ticket including its comments' indicate retrieval/query of existing data with no modifications or deletions.
Attacks that exploit this kind of access
Get full detail of a Zendesk ticket including its comments. 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_get_ticket: 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_get_ticket 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_get_ticket 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_get_ticket. 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_get_ticket 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 →