AI agents use add_memory to create or update resources in MCP RAG — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP RAG environment.
This tool modifies the agent's memory state by inserting new information, making it a Write category action. The severity is medium because misuse could lead to the agent operating on corrupted, irrelevant, or adversarial information injected into its memory, affecting decision-making. However, it's not destructive since memory entries can be removed, and it doesn't execute code or access financial systems.
From the tool's definition The tool is named "add_memory" and described as "Add information to the agent memory system". The verb "Add" indicates creation/insertion of data into a vector memory store (ChromaDB), which is a reversible write operation.
Attacks that exploit this kind of access
Add information to the agent memory system. It is categorised as a Write tool in the MCP RAG MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP RAG MCP server in PolicyLayer and add a rule for add_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 MCP RAG. Nothing to install.
add_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_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_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_memory is provided by the MCP RAG MCP server (santis84/mcp-rag). 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 →