List trigger nodes from the imported n8n catalog.
AI agents call list_triggers to retrieve information from N8n Workflow Tester Safe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from a catalog with no side effects. It does not create, modify, delete, or execute workflows or any operations. The blast radius of misuse is minimal—an agent could only view what trigger nodes are available in the catalog, which is informational data with no security or operational impact.
From the tool's definition Tool name 'list_triggers' and description 'List trigger nodes from the imported n8n catalog' indicate a retrieval/query operation that returns information about available trigger nodes without modifying or executing anything.
Attacks that exploit this kind of access
List trigger nodes from the imported n8n catalog. It is categorised as a Read tool in the N8n Workflow Tester Safe MCP Server, which means it retrieves data without modifying state.
Register the N8n Workflow Tester Safe 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 N8n Workflow Tester Safe. 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 N8n Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). 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 →