AI agents call get_stats to retrieve information from Engram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns summary statistics about stored memories without modifying, deleting, or executing any operations. It has no side effects and presents minimal risk—an agent obtaining memory statistics cannot cause harm through this tool alone. Low severity due to no blast radius from misuse.
From the tool's definition Tool returns aggregated statistics from the database: total count, category counts, top tags, oldest/newest memory dates, average content length, and untagged/unmetadata memories. Uses 'Devuelve' (returns) indicating data retrieval with no modification.
Attacks that exploit this kind of access
Devuelve estadísticas agregadas de la base de datos: total, conteo por categoría, top tags, memoria más antigua y más reciente, longitud promedio de contenido, y memorias sin tags o sin metadata. It is categorised as a Read tool in the Engram MCP Server, which means it retrieves data without modifying state.
Register the Engram MCP server in PolicyLayer and add a rule for get_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 Engram. Nothing to install.
get_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 get_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 get_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.
get_stats is provided by the Engram MCP server (jacksini/engram-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 →