AI agents call get_trigger 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 information about a Zendesk trigger (automation rules) by querying an existing trigger ID. It performs a read-only lookup operation that does not create, modify, delete, or execute any actions. No data is changed and no external operations are triggered. This is a straightforward data retrieval use case, posing minimal risk even if called unexpectedly by an AI agent.
From the tool's definition The tool name is 'get_trigger' and the description states 'Get full details of a single Zendesk trigger by ID.' The verb 'Get' and the phrase 'full details' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get full details of a single Zendesk trigger by ID. 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_trigger: 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_trigger 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_trigger 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_trigger. 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_trigger is provided by the Zendesk MCP server (kalchevs/zendesk-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 →