Create a relation between two nodes. Supports 22 relation types:
AI agents use graph_add_relation 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.
This tool creates new relations in a persistent graph-based memory system, which is a reversible modification (relations can be deleted via sibling tool graph_delete_node). It does not execute external code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Create a relation between two nodes' — a creation operation that modifies the graph structure by adding new relational data.
Attacks that exploit this kind of access
Create a relation between two nodes. Supports 22 relation types:. 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_relation: 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_relation 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_relation 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_relation. 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_relation 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 →