AI agents call stats to retrieve information from Memex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'stats' typically indicates statistics gathering or reporting, which is a read operation with no side effects. However, the empty description creates ambiguity about whether it queries internal memory state, system metrics, or something else.
From the tool's definition Tool name 'stats' combined with context of a memory/MCP gateway server suggests data retrieval or metrics reporting. No description provided to confirm, lowering confidence.
Attacks that exploit this kind of access
stats. It is categorised as a Read tool in the Memex MCP Server, which means it retrieves data without modifying state.
Register the Memex MCP server in PolicyLayer and add a rule for 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 Memex. Nothing to install.
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 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 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.
stats is provided by the Memex MCP server (queflyhq/memex). 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 →