AI agents call n2n_delete_entities to permanently remove resources in N2n Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Delete operations are irreversible and permanently remove data from the knowledge graph. Even without a full description, the name unambiguously indicates destructive capability. This rates as Destructive (not just Write) because deletion cannot be undone. Severity is high because an AI agent misusing this could permanently erase project memory/knowledge without recovery.
From the tool's definition Tool name is 'n2n_delete_entities' with no description provided. The verb 'delete' combined with 'entities' in a knowledge graph context indicates irreversible removal of data nodes.
Documented attack patterns abuse exactly the kind of access n2n_delete_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for n2n_delete_entities:
{
"version": "1",
"default": "deny",
"hide": [
"n2n_delete_entities"
]
}n2n_delete_entities 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.
n2n_delete_entities. It is categorised as a Destructive tool in the N2n Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the N2n Memory MCP server in PolicyLayer and add a rule for n2n_delete_entities: 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 N2n Memory. Nothing to install.
n2n_delete_entities 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 n2n_delete_entities 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 n2n_delete_entities. 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.
n2n_delete_entities is provided by the N2n Memory MCP server (n2ns/n2n-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N2n Memory, 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.
12 N2n Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.