get_memory_stats

THE RISK

Low Risk

Why get_memory_stats needs a policy

This tool performs a read-only retrieval of system statistics. It does not create, modify, delete, or execute any operations. The information returned is descriptive metadata about the graph structure, making it a straightforward Read category operation with low severity since disclosure of aggregate statistics poses minimal risk.

From the tool's definition Tool name is "get_memory_stats" and description states it "Returns statistics about the memory system (number of nodes, edges, etc.)" — a query operation that retrieves aggregate metrics without modifying, executing external operations, or causing side…

Documented attack patterns abuse exactly the kind of access get_memory_stats gives an agent:

POLICY

How to control get_memory_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and A-MEM: Agentic Memory System, and nothing reaches the server without passing your rules. This is the rule we recommend for get_memory_stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_memory_stats": {}
  }
}

get_memory_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register A-MEM: Agentic Memory System — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More A-MEM: Agentic Memory System tools

Destructive delete_atomic_note Deletes a note from the memory system. Removes the note from Graph and Vector Store as wel Destructive remove_relation Removes a relation between two notes. Destructive reset_memory Resets the complete memory system (Graph + Vector Store). Deletes all notes, edges, and em Execute run_memory_enzymes Runs comprehensive memory maintenance enzymes: repairs corrupted nodes, prunes old/weak li Execute research_and_store Performs deep web research on a query and stores the findings as atomic notes. Uses Google Write add_file Stores the content of a file (e.g., .md) as a note in the memory system. Supports automati Write add_relation Adds a manual relation between two notes. Write create_atomic_note Stores a new piece of information in the memory system. Automatically classifies the note

All 15 A-MEM: Agentic Memory System tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_memory_stats

What does the get_memory_stats tool do? +

Returns statistics about the memory system (number of nodes, edges, etc.). It is categorised as a Read tool in the A-MEM: Agentic Memory System MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_memory_stats? +

Register the A-MEM: Agentic Memory System MCP server in PolicyLayer and add a rule for get_memory_stats: 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 A-MEM: Agentic Memory System. Nothing to install.

What risk level is get_memory_stats? +

get_memory_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_memory_stats? +

Yes. Add a rate_limit block to the get_memory_stats 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.

How do I block get_memory_stats completely? +

Set action: deny in the PolicyLayer policy for get_memory_stats. 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.

What MCP server provides get_memory_stats? +

get_memory_stats is provided by the A-MEM: Agentic Memory System MCP server (tobs-code/a-mem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every A-MEM: Agentic Memory System tool call.

Start from A-MEM: Agentic Memory System, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →