add_memory
Add an episode to the knowledge graph
Part of the Graphiti MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents use add_memory to create or modify resources in Graphiti. 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.
WHY ENFORCE A POLICY ON ADD_MEMORY
Without a policy, an AI agent could call add_memory repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Graphiti.
RECOMMENDED POLICY
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
add_memory:
rules:
- action: allow
rate_limit:
max: 30
window: 60 See the full Graphiti policy for all 9 tools.
DETAILS
MORE GRAPHITI TOOLS
search_nodes Read search_memory_facts Read get_episodes Read get_entity_edge Read get_status Read delete_entity_edge Destructive delete_episode Destructive clear_graph Destructive SIMILAR WRITE TOOLS ON OTHER SERVERS
RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the add_memory tool do?
Add an episode to the knowledge graph. It is categorised as a Write tool in the Graphiti MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
How do I enforce a policy on add_memory?
Add a rule in your Intercept YAML policy under the tools section for add_memory. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Graphiti MCP server.
What risk level is add_memory?
add_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Can I rate-limit add_memory?
Yes. Add a rate_limit block to the add_memory rule in your Intercept 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.
How do I block add_memory completely?
Set action: deny in the Intercept 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.
What MCP server provides add_memory?
add_memory is provided by the Graphiti MCP server (getzep/graphiti). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON GRAPHITI
Open source. One binary. Zero dependencies.