Uninstall a community node package
AI agents call community_node_uninstall to permanently remove resources in N8n Fabric — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Uninstalling a community node package is a destructive action that removes installed software from the n8n workflow platform. This cannot be easily undone without reinstalling, and it may break workflows that depend on that node. The impact is permanent system modification with potential side effects on dependent automations, justifying Destructive classification over Write.
From the tool's definition 'Uninstall a community node package' — removes a workflow component irreversibly, affecting automation infrastructure.
Attacks that exploit this kind of access
Uninstall a community node package. It is categorised as a Destructive tool in the N8n Fabric MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N8n Fabric MCP server in PolicyLayer and add a rule for community_node_uninstall: 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 Fabric. Nothing to install.
community_node_uninstall 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 community_node_uninstall 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 community_node_uninstall. 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.
community_node_uninstall is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). 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 →