AI agents call get_ticket_attachment to retrieve information from Zendesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing attachment data from Zendesk tickets. It does not create, modify, delete, or execute any operations—it only queries and returns information. This is a typical Read operation similar to other get_* tools on the server (get_ticket, get_ticket_comments, get_tickets). The blast radius of misuse is minimal since it merely retrieves data already accessible through ticket comments.
From the tool's definition Tool description states 'Fetch a Zendesk ticket attachment' and returns 'file as base64-encoded data'. The verb 'Fetch' and the action of retrieving and returning existing attachment data indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Fetch a Zendesk ticket attachment by its content_url and return the file as base64-encoded data. Use the attachment URLs returned by get_ticket_comments. It is categorised as a Read tool in the Zendesk MCP Server, which means it retrieves data without modifying state.
Register the Zendesk MCP server in PolicyLayer and add a rule for get_ticket_attachment: 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. Nothing to install.
get_ticket_attachment 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_attachment 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_attachment. 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_attachment is provided by the Zendesk MCP server (reminia/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 →