n8n_uninstall_community_package

Uninstall a community node package. Workflows using its nodes will break. Args: - packageName (string): npm package name to uninstall

Server n8n MCP Server verzth/mcp-n8n
Category Destructive
Risk class Critical
Parameters 00 required

What n8n_uninstall_community_package does on n8n MCP Server

AI agents call n8n_uninstall_community_package 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.

Why n8n_uninstall_community_package needs a policy

Uninstalling a community package is an irreversible action that destroys the operational integrity of dependent workflows. While the package can theoretically be reinstalled, the immediate effect is destructive breakage. This is more severe than Write (which is reversible) because it causes cascading failures across dependent systems and cannot be easily undone without manual workflow repairs.

From the tool's definition Tool name contains 'uninstall' and description states 'Workflows using its nodes will break' — indicating irreversible removal of functionality that causes dependent workflows to fail.

Questions about n8n_uninstall_community_package

What does the n8n_uninstall_community_package tool do? +

Uninstall a community node package. Workflows using its nodes will break. Args: - packageName (string): npm package name to uninstall. 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.

How do I enforce a policy on n8n_uninstall_community_package? +

Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_uninstall_community_package: 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.

What risk level is n8n_uninstall_community_package? +

n8n_uninstall_community_package is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit n8n_uninstall_community_package? +

Yes. Add a rate_limit block to the n8n_uninstall_community_package 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.

How do I block n8n_uninstall_community_package completely? +

Set action: deny in the PolicyLayer policy for n8n_uninstall_community_package. 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.

What MCP server provides n8n_uninstall_community_package? +

n8n_uninstall_community_package is provided by the n8n MCP Server MCP server (verzth/mcp-n8n). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.