Process selected queued pi captures into curated Memento notes. Requires explicit selection; use dryRun to preview.
AI agents use memento_process to create or update resources in Memento Vault — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memento Vault environment.
This tool takes queued captures and writes them as curated notes into the vault. It creates or modifies persistent data (notes), making it a Write operation. The dryRun option confirms that the non-dry execution path performs actual writes. It is not Destructive (no deletion implied), not Execute (no code/commands run), and not merely a read.
From the tool's definition 'Process selected queued captures into curated Memento notes' — converts/writes queued items into persistent notes; 'dryRun to preview' confirms actual write path exists
Documented attack patterns abuse exactly the kind of access memento_process 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_process:
{
"version": "1",
"default": "deny",
"tools": {
"memento_process": {
"limits": [
{
"counter": "memento_process_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memento_process stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Process selected queued pi captures into curated Memento notes. Requires explicit selection; use dryRun to preview. It is categorised as a Write tool in the Memento Vault MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memento Vault MCP server in PolicyLayer and add a rule for memento_process: 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_process is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the memento_process 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_process. 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_process 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.