AI agents call n2n_get_graph_summary to retrieve information from N2n Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and summarizes information from the persisted knowledge graph without modifying it. No side effects are indicated. The name structure and positioning among sibling tools strongly suggest a query/retrieval function rather than a creation, modification, or deletion operation. Description is empty, but naming convention and context are sufficient for high confidence classification as Read.
From the tool's definition Tool name 'n2n_get_graph_summary' indicates a retrieval/summary operation on the knowledge graph. The sibling tools show a clear pattern: read operations (n2n_read_graph, n2n_search, n2n_open_nodes, n2n_export_markdown) versus write/delete operations…
Documented attack patterns abuse exactly the kind of access n2n_get_graph_summary 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_get_graph_summary:
{
"version": "1",
"default": "deny",
"tools": {
"n2n_get_graph_summary": {}
}
}n2n_get_graph_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
n2n_get_graph_summary. It is categorised as a Read tool in the N2n Memory MCP Server, which means it retrieves data without modifying state.
Register the N2n Memory MCP server in PolicyLayer and add a rule for n2n_get_graph_summary: 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_get_graph_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the n2n_get_graph_summary 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_get_graph_summary. 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_get_graph_summary 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.