Get your usage statistics. Memory count, total size, last access
AI agents call memory.stats to retrieve information from Sylex Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves statistical metadata about the user's own memory consumption. It has no side effects, does not create or modify data, does not execute code or external operations, and does not delete anything. The blast radius of misuse is minimal—an agent could only read statistics that belong to the user anyway. This is a straightforward Read operation.
From the tool's definition Tool name 'memory.stats' and description 'Get your usage statistics. Memory count, total size, last access' indicate a query operation that retrieves aggregate statistics about the user's memory usage without modifying, executing external operations, or…
Attacks that exploit this kind of access
Get your usage statistics. Memory count, total size, last access. It is categorised as a Read tool in the Sylex Memory MCP Server, which means it retrieves data without modifying state.
Register the Sylex Memory 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 Sylex Memory. 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 Sylex Memory MCP server (mastadoonprime/sylex-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →