Get statistics about stored observations: totals, counts by type, by project, by importance.
AI agents call memory_stats to retrieve information from GraphHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves and reports statistics from memory/observations. There are no side effects, data modifications, code execution, or destructive operations. It aligns with the 'Read' category pattern of retrieving or querying data. The low severity reflects that misuse would expose analytics metadata without enabling state changes or resource exhaustion risks.
From the tool's definition Tool name 'memory_stats' and description 'Get statistics about stored observations: totals, counts by type, by project, by importance' indicate a retrieval operation that queries aggregate data without modification.
Documented attack patterns abuse exactly the kind of access memory_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GraphHub, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_stats:
{
"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.
Free to start. No card required.
Get statistics about stored observations: totals, counts by type, by project, by importance. It is categorised as a Read tool in the GraphHub MCP Server, which means it retrieves data without modifying state.
Register the GraphHub 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 GraphHub. Nothing to install.
memory_stats 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 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.
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.
memory_stats is provided by the GraphHub MCP server (slnquangtran/graph-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GraphHub, 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.
32 GraphHub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.