store_memento
AI agents use store_memento to create or update resources in MCP Memento — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memento environment.
'store_memento' most likely creates or saves a new memory/knowledge entry in the persistent store, which is a Write operation. The description is empty, so confidence is reduced, but the server context and naming convention strongly imply creating/writing data rather than reading or executing. It is reversible (sibling tool 'delete_memento' exists), so Destructive is not applicable.
From the tool's definition Tool name 'store_memento' on a server described as enabling 'storing and recalling solutions, facts, and decisions' — sibling tools include delete_memento, create_memento_relationship, boost/adjust confidence tools.
Attacks that exploit this kind of access
store_memento. It is categorised as a Write tool in the MCP Memento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Memento MCP server in PolicyLayer and add a rule for store_memento: 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 MCP Memento. Nothing to install.
store_memento 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 store_memento 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 store_memento. 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.
store_memento is provided by the MCP Memento MCP server (x-hannibal/mcp-memento). 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 →