Add episodic memories into your vector store to be searchable at a later time. These memories are NOT part of your memory about the user, and will be stored in a vector DB until retrieved explicitly with the vector search tool.
Part of the Memory server.
Free to start. No card required.
AI agents use add_vector_memory to create or modify resources in Memory. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call add_vector_memory repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Memory.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"add_vector_memory": {
"limits": [
{
"counter": "add_vector_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Memory policy for all 5 tools.
These attack patterns abuse exactly the kind of access add_vector_memory gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Add episodic memories into your vector store to be searchable at a later time. These memories are NOT part of your memory about the user, and will be stored in a vector DB until retrieved explicitly with the vector search tool.. It is categorised as a Write tool in the Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory MCP server in PolicyLayer and add a rule for add_vector_memory: 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 Memory. Nothing to install.
add_vector_memory 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 add_vector_memory 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 add_vector_memory. 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.
add_vector_memory is provided by the Memory MCP server (@letta-ai/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.