AI agents call remove to permanently remove resources in Npm — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
A 'remove' operation on a package manager irreversibly removes packages from the project dependencies. While node_modules can be reinstalled, the removal modifies package.json and lockfiles and could break builds.
From the tool's definition Tool name is 'remove' on an npm/pnpm operations server, implying removal/uninstallation of packages
Documented attack patterns abuse exactly the kind of access remove gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Npm, and nothing reaches the server without passing your rules. This is the rule we recommend for remove:
{
"version": "1",
"default": "deny",
"hide": [
"remove"
]
} remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Runs. It is categorised as a Destructive tool in the Npm MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Npm MCP server in PolicyLayer and add a rule for remove: 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 Npm. Nothing to install.
remove 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 remove 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 remove. 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.
remove is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Npm, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Npm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.