Delete a product by its ID
AI agents call delete_product to permanently remove resources in MCP Node Js TypeScript API — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on persistent data. Even though the blast radius depends on context (e.g., how many products are affected, business criticality), deletion of products from a database cannot be undone without backups or transaction logs. This qualifies as Destructive, the most severe category applicable.
From the tool's definition Tool name is 'delete_product' and description states 'Delete a product by its ID' — this irreversibly removes data from the MongoDB database.
Attacks that exploit this kind of access
Delete a product by its ID. It is categorised as a Destructive tool in the MCP Node Js TypeScript API MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Node Js TypeScript API MCP server in PolicyLayer and add a rule for delete_product: 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 MCP Node Js TypeScript API. Nothing to install.
delete_product 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 delete_product 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 delete_product. 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.
delete_product is provided by the MCP Node Js TypeScript API MCP server (proffillipesilva/mcpnodefil). 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 →