🗑️ Clear template cache.
AI agents call clear_template_cache to permanently remove resources in n8n Workflow Builder — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache is an irreversible operation that destroys currently stored template data. While caches can be rebuilt, the act itself is non-undoable and could disrupt workflow building operations that rely on cached templates. Severity is medium because cache loss is recoverable through re-fetching, but could cause disruption.
From the tool's definition 🗑️ Clear template cache — 'clear' and the trash/delete emoji indicate irreversible removal of cached data
Attacks that exploit this kind of access
🗑️ Clear template cache. It is categorised as a Destructive tool in the n8n Workflow Builder MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for clear_template_cache: 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 Builder. Nothing to install.
clear_template_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_template_cache 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 clear_template_cache. 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.
clear_template_cache is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →