Show memento vault and lifecycle bridge health/config status. Use for operational checks and setup debugging, not for prior decisions, project history, or note content; use memento_search and memento_get for recall.
AI agents call memento_status to retrieve information from Memento Vault without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
memento_status retrieves operational metadata and system health information about the vault infrastructure. It performs no data modification, code execution, or destructive actions—it only queries and displays status. This is a diagnostic/monitoring tool, firmly in the Read category.
From the tool's definition Tool description states it is used to "Show memento vault and lifecycle bridge health/config status" for "operational checks and setup debugging".
Documented attack patterns abuse exactly the kind of access memento_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memento Vault, and nothing reaches the server without passing your rules. This is the rule we recommend for memento_status:
{
"version": "1",
"default": "deny",
"tools": {
"memento_status": {}
}
}memento_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show memento vault and lifecycle bridge health/config status. Use for operational checks and setup debugging, not for prior decisions, project history, or note content; use memento_search and memento_get for recall. It is categorised as a Read tool in the Memento Vault MCP Server, which means it retrieves data without modifying state.
Register the Memento Vault MCP server in PolicyLayer and add a rule for memento_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 Memento Vault. Nothing to install.
memento_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 memento_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 memento_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.
memento_status is provided by the Memento Vault MCP server (sandsower/memento-vault). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memento Vault, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Memento Vault tools catalogued and risk-classified — across an index of 43,000+ MCP servers.