Delete a project
AI agents call n8n_delete_project to permanently remove resources in n8n MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a project in n8n removes project configuration, workflows, and associated data permanently and cannot be undone. This falls squarely into the Destructive category as it irreversibly removes data at scale. The severity is high because a project deletion could affect multiple workflows and users depending on that project, though the blast radius is scoped to one project rather than entire instance data.
From the tool's definition Tool name is 'n8n_delete_project' with description 'Delete a project'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a project. It is categorised as a Destructive tool in the n8n MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_delete_project: 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 MCP Server. Nothing to install.
n8n_delete_project 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 n8n_delete_project 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 n8n_delete_project. 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.
n8n_delete_project is provided by the n8n MCP Server MCP server (shravan1610/n8n-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 →