Get statistics about the Midos memory system (LanceDB chunks, cache status).
AI agents call memory_stats to retrieve information from MidOS - MCP Community Library without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries internal statistics and status information about a memory system (LanceDB chunks, cache). It has no side effects, does not modify data, does not execute code, and does not move money. It is purely informational retrieval, fitting the Read category with low severity.
From the tool's definition Tool name 'memory_stats' and description 'Get statistics about the Midos memory system' indicate retrieval of monitoring/observability data. Verbs are 'Get' and 'about', with no mutation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get statistics about the Midos memory system (LanceDB chunks, cache status). It is categorised as a Read tool in the MidOS - MCP Community Library MCP Server, which means it retrieves data without modifying state.
Register the MidOS - MCP Community Library 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 MidOS - MCP Community Library. 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 MidOS - MCP Community Library MCP server (midos-mcp). 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 →