Store a new memory in the knowledge base. Use this to remember facts, preferences, instructions, or context for future interactions.
AI agents use memory_store to create or update resources in MCP Router — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Router environment.
This tool creates/writes new data to a persistent knowledge base. It does not delete or overwrite existing records (that appears to be memory_delete), and it does not execute code or move money. Misuse could allow an AI agent to inject false facts or malicious instructions into the knowledge base, affecting future interactions — hence medium severity.
From the tool's definition 'Store a new memory in the knowledge base. Use this to remember facts, preferences, instructions, or context for future interactions.'
Attacks that exploit this kind of access
Store a new memory in the knowledge base. Use this to remember facts, preferences, instructions, or context for future interactions. It is categorised as a Write tool in the MCP Router MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Router MCP server in PolicyLayer and add a rule for memory_store: 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 Router. Nothing to install.
memory_store 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 memory_store 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 memory_store. 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.
memory_store is provided by the MCP Router MCP server (justinpreston/mcp-router). 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 →