graph_decompose · MCP Roo Memory MCP: Risk & Policy

WHAT IT DOES

What graph_decompose does on MCP Roo Memory

AI agents use graph_decompose 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.

WHY IT NEEDS A POLICY

Why graph_decompose needs a policy

This tool writes new data to the persistent graph by creating subtask nodes and establishing relations between them. It does not delete or overwrite existing data irreversibly, nor does it execute code or involve financial operations. The blast radius is medium since misuse could pollute the knowledge graph with incorrect task decompositions that affect downstream reasoning.

From the tool's definition 'Creates subtask nodes and adds decomposes_to relations' — the tool creates new nodes and relationships in the graph

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

graph_decompose Rate-limited

graph_decompose 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "graph_decompose": {
      "limits": [
        {
          "counter": "graph_decompose_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Roo Memory, so you can run agents against it safely.

FAQ

Questions about graph_decompose

What does the graph_decompose tool do? +

Decompose a task node into subtasks. Creates subtask nodes and adds decomposes_to relations. 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.

How do I enforce a policy on graph_decompose? +

Register the MCP Roo Memory MCP server in PolicyLayer and add a rule for graph_decompose: 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.

What risk level is graph_decompose? +

graph_decompose is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit graph_decompose? +

Yes. Add a rate_limit block to the graph_decompose 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.

How do I block graph_decompose completely? +

Set action: deny in the PolicyLayer policy for graph_decompose. 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 graph_decompose? +

graph_decompose 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.