AI agents use add_memory to create or update resources in Graphiti MCP Demo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Graphiti MCP Demo environment.
The tool name 'add_memory' clearly indicates creation or modification of data within the knowledge graph. Absence of language like 'delete', 'drop', or 'destroy' places it in Write rather than Destructive. The empty description lowers confidence slightly, but the name is sufficiently clear.
From the tool's definition Tool name 'add_memory' with empty description, combined with sibling tools 'delete_entity_edge', 'delete_episode', and 'clear_graph' indicating data manipulation capabilities.
Documented attack patterns abuse exactly the kind of access add_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Graphiti MCP Demo, and nothing reaches the server without passing your rules. This is the rule we recommend for add_memory:
{
"version": "1",
"default": "deny",
"tools": {
"add_memory": {
"limits": [
{
"counter": "add_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_memory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
add_memory. It is categorised as a Write tool in the Graphiti MCP Demo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Graphiti MCP Demo 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 Graphiti MCP Demo. 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 Graphiti MCP Demo MCP server (kartikk-26/graphiti-mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Graphiti MCP Demo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Graphiti MCP Demo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.