memory_stats

THE RISK

Low Risk

Why memory_stats needs a policy

This tool queries and returns statistics about an existing memory file's state and optimization status. It performs no writes, deletions, code execution, or financial operations. It is purely informational/diagnostic in nature, making it a Read operation with low severity.

From the tool's definition Tool name 'memory_stats' and description 'Get detailed statistics and optimization status' indicate retrieval of status information with no modification or side effects.

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

POLICY

How to control memory_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Mode Manager MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_stats:

policy.json

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

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 Mode Manager MCP — 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 Mode Manager MCP tools

Destructive delete_instruction Delete a VS Code .instructions.md file from the prompts directory. Write configure_memory_optimization Configure memory optimization settings for auto-optimization behavior. Write create_instruction Create a new VS Code .instructions.md file with the specified description and content. Write optimize_memory Manually optimize a memory file using AI to reorganize and consolidate entries while prese Write remember remember Write update_instruction Update an existing VS Code .instructions.md file with new description or content. Read get_instruction Get the raw content of a VS Code .instructions.md file. Read list_instructions List all VS Code .instructions.md files in the prompts directory.

All 9 Mode Manager MCP 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 memory_stats

What does the memory_stats tool do? +

Get detailed statistics and optimization status for a memory file. It is categorised as a Read tool in the Mode Manager MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_stats? +

Register the Mode Manager MCP server in PolicyLayer and add a rule for 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 Mode Manager MCP. Nothing to install.

What risk level is memory_stats? +

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

Can I rate-limit memory_stats? +

Yes. Add a rate_limit block to the 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 memory_stats completely? +

Set action: deny in the PolicyLayer policy for 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 memory_stats? +

memory_stats is provided by the Mode Manager MCP server (niclasolofsson/mode-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mode Manager MCP tool call.

Start from Mode Manager MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →