Supersede an old node with a new one (Strategy B: Supersedes).
AI agents call graph_supersede to retrieve information from MCP Roo Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though graph_supersede only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Supersede an old node with a new one (Strategy B: Supersedes). It is categorised as a Read tool in the MCP Roo Memory MCP Server, which means it retrieves data without modifying state.
Register the MCP Roo Memory MCP server in PolicyLayer and add a rule for graph_supersede: 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_supersede is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the graph_supersede 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_supersede. 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_supersede 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 →