AI agents call list_triggers 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 displays trigger metadata (conditions and actions) without executing, modifying, creating, or deleting triggers. While triggers themselves are automation rules that execute actions, this tool only reads and displays their configuration. The most severe risk is information disclosure about business automation rules, which is low severity in a tool-classification context.
From the tool's definition Tool name 'list_triggers' and description 'List all Zendesk triggers' indicate a retrieval operation that queries existing Zendesk trigger configurations. The verb 'list' is a clear read operation with no modification or execution of those triggers.
Attacks that exploit this kind of access
List all Zendesk triggers (business rules) with conditions and actions. 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 list_triggers: 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.
list_triggers 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 list_triggers 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 list_triggers. 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.
list_triggers 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 →