roam_move_block
Move a block to a new location (different parent or position). This is a convenience wrapper around
This record as markdown: /tools/2b3pro-roam-research-mcp/roam-move-block.md
What roam_move_block does on Roam Research
AI agents use roam_move_block to create or update resources in Roam Research, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Roam Research environment.
Why roam_move_block is rated Medium
This tool modifies existing data by relocating blocks within the Roam Research graph—a reversible write operation. While not destructive (the block still exists, just repositioned), it represents a Write category action as it alters the organizational structure of the user's knowledge base.
From the tool's definition Tool description states 'Move a block to a new location (different parent or position)' which modifies the structure and location of data within the graph. The verb 'move' indicates a write operation that changes data state.
Attacks that exploit this kind of access
The rule that runs roam_move_block safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Roam Research, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For roam_move_block, this is the rule to start with:
roam_move_block 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Roam Research, apply this rule, and every roam_move_block call is checked against it from then on.
Questions about roam_move_block
Move a block to a new location (different parent or position). This is a convenience wrapper around. It is categorised as a Write tool in the Roam Research MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Roam Research MCP server in PolicyLayer and add a rule for roam_move_block: 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 Roam Research. Nothing to install.
roam_move_block 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 roam_move_block 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 roam_move_block. 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.
roam_move_block is provided by the Roam Research MCP server (2b3pro/roam-research-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Roam Research, and thousands of servers like it.
This server
Across the catalogue