Add a node to the knowledge graph. Supports 13 types (entity, fact, decision, thought,
AI agents use graph_add_node to create or update resources in MCP Roo Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Roo Memory environment.
The tool creates new nodes in a graph-based memory system. This is a Write operation because it adds data that can be subsequently modified or deleted (as evidenced by sibling tools like graph_delete_node and graph_supersede). It does not execute arbitrary code, delete irreversibly, move funds, or read without side effects.
From the tool's definition Tool name 'graph_add_node' and description 'Add a node to the knowledge graph' indicate creation of new data structures. This is a reversible modification operation.
Attacks that exploit this kind of access
Add a node to the knowledge graph. Supports 13 types (entity, fact, decision, thought,. It is categorised as a Write tool in the MCP Roo Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Roo Memory MCP server in PolicyLayer and add a rule for graph_add_node: 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 Roo Memory. Nothing to install.
graph_add_node 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 graph_add_node 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 graph_add_node. 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.
graph_add_node is provided by the MCP Roo Memory MCP server (mcasdfgf/mcp-roo-memory). 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 →