List queued pi capture candidates from lifecycle or manual capture review. Use for capture workflow review, not for searching prior decisions or project history.
AI agents call memento_queue 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.
The tool performs a retrieval operation (listing queued items) with no side effects. It does not create, modify, delete, or execute operations. The explicit statement 'for capture workflow review' indicates passive inspection of existing queue state. This is a classic Read category tool with low blast radius if misused by an AI agent.
From the tool's definition Tool description states 'List queued pi capture candidates' and 'for capture workflow review' - this is a read/query operation that retrieves information about pending items in a queue without modifying or deleting them.
Documented attack patterns abuse exactly the kind of access memento_queue 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_queue:
{
"version": "1",
"default": "deny",
"tools": {
"memento_queue": {}
}
}memento_queue 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.
List queued pi capture candidates from lifecycle or manual capture review. Use for capture workflow review, not for searching prior decisions or project history. 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_queue: 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_queue 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_queue 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_queue. 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_queue 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.