roam_fetch_block
Fetch a block by its UID with optional children (down to a specified depth) and/or ancestors (up to page root). Returns the block\
This record as markdown: /tools/2b3pro-roam-research-mcp/roam-fetch-block.md
What roam_fetch_block does on Roam Research
AI agents call roam_fetch_block to retrieve information from Roam Research without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why roam_fetch_block is rated Low
This tool retrieves and returns block data from Roam Research by UID. It supports optional parameters to fetch related data (children/ancestors) but performs no create, update, delete, or execute operations. The singular purpose of fetching data with no state modification qualifies it as a Read operation with minimal risk.
From the tool's definition Tool name 'roam_fetch_block' and description 'Fetch a block by its UID with optional children... and/or ancestors... Returns the block' indicate retrieval of existing data only.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs roam_fetch_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_fetch_block, this is the rule to start with:
roam_fetch_block is read-only, so it stays allowed. 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_fetch_block call is checked against it from then on.
Questions about roam_fetch_block
Fetch a block by its UID with optional children (down to a specified depth) and/or ancestors (up to page root). Returns the block\. It is categorised as a Read tool in the Roam Research MCP Server, which means it retrieves data without modifying state.
Register the Roam Research MCP server in PolicyLayer and add a rule for roam_fetch_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_fetch_block 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 roam_fetch_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_fetch_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_fetch_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