memory_stats

SERVERRuflo SOURCEruvnet/ruflo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ruflo/memory-stats.md

WHAT IT DOES

What memory_stats does on Ruflo

AI agents call memory_stats to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why memory_stats is rated Low

The tool retrieves statistical information about memory storage and index status. This is a read-only operation that queries and returns metadata/metrics without modifying any data or triggering side effects.

From the tool's definition Get memory storage statistics including HNSW index status

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_stats, this is the rule to start with:

memory_stats Allowed

memory_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every memory_stats call is checked against it from then on.

FAQ

Questions about memory_stats

What does the memory_stats tool do? +

Get memory storage statistics including HNSW index status Use when native Read/Write is wrong because you need (a) cross-session retrieval by semantic similarity (vector embeddings) not by file path, (b) namespacing across projects without managing directory layout, or (c) the .swarm/memory.db audit trail. For one-shot file I/O, native Read/Write is fine. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_stats? +

Register the Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →