Add new knowledge to the personal brain. Content is embedded and stored for future semantic retrieval.
AI agents use add_memory to create or update resources in Open Brain MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Brain MCP Server environment.
This tool creates and stores new data (memories) in a persistent semantic knowledge base. It is clearly a Write operation as it modifies the state of the brain by adding new entries.
From the tool's definition Tool description states 'Add new knowledge to the personal brain' and 'stored for future semantic retrieval', indicating it creates and persists new data entries in the knowledge base.
Attacks that exploit this kind of access
Add new knowledge to the personal brain. Content is embedded and stored for future semantic retrieval. It is categorised as a Write tool in the Open Brain MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Brain MCP Server 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 Open Brain MCP Server. 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 Open Brain MCP Server MCP server (subwizzll/mcp-server). 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 →