AI agents call mementos_storage_status to retrieve information from Mementos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only introspection of system state (database and storage sync status). It has no side effects, does not execute code or external operations, and does not modify or delete data. The blast radius of misuse is minimal—an AI agent could at worst gather information about storage sync status, which poses no security risk.
From the tool's definition Tool name 'mementos_storage_status' and description 'Show mementos local database and remote storage sync status' indicates a query/inspection operation that retrieves and displays status information without modifying any data.
Attacks that exploit this kind of access
Show mementos local database and remote storage sync status. It is categorised as a Read tool in the Mementos MCP Server, which means it retrieves data without modifying state.
Register the Mementos MCP server in PolicyLayer and add a rule for mementos_storage_status: 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 Mementos. Nothing to install.
mementos_storage_status 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 mementos_storage_status 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 mementos_storage_status. 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.
mementos_storage_status is provided by the Mementos MCP server (@hasna/mementos). 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 →