AI agents use n2n_add_entities to create or update resources in N2n Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N2n Memory environment.
The 'add_entities' operation creates or inserts new data (entities) into a persisted knowledge graph within a project directory. This is reversible via the sibling 'n2n_delete_entities' tool, making it Write rather than Destructive. The blast radius is medium: an agent adding arbitrary entities could pollute the project's memory graph, but the effect is confined to a single project and can be undone.
From the tool's definition Tool name 'n2n_add_entities' indicates creation of new entities in a knowledge graph. Sibling tools include 'n2n_delete_entities', 'n2n_delete_observations', and 'n2n_delete_relations', confirming this server manages persistent graph data.
Documented attack patterns abuse exactly the kind of access n2n_add_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_add_entities:
{
"version": "1",
"default": "deny",
"tools": {
"n2n_add_entities": {
"limits": [
{
"counter": "n2n_add_entities_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}n2n_add_entities stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
n2n_add_entities. It is categorised as a Write tool in the N2n Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N2n Memory MCP server in PolicyLayer and add a rule for n2n_add_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_add_entities is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the n2n_add_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_add_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_add_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.