roam_search_by_status
Search for blocks with a specific status (TODO/DONE) across all pages or within a specific page.
This record as markdown: /tools/2b3pro-roam-research-mcp/roam-search-by-status.md
What roam_search_by_status does on Roam Research
AI agents call roam_search_by_status 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_search_by_status is rated Low
This tool performs a search query to find and retrieve blocks based on their status attribute. It has no side effects—it only fetches and returns matching data. The verb 'search' and the absence of any modification, deletion, or execution language confirm this is a Read operation with low severity since misuse would only expose existing data without enabling destructive or financial harm.
From the tool's definition Tool name 'roam_search_by_status' and description 'Search for blocks with a specific status (TODO/DONE) across all pages or within a specific page' indicates a read-only query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
The rule that runs roam_search_by_status 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_search_by_status, this is the rule to start with:
roam_search_by_status 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_search_by_status call is checked against it from then on.
Questions about roam_search_by_status
Search for blocks with a specific status (TODO/DONE) across all pages or within a specific page. 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_search_by_status: 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_search_by_status 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_search_by_status 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_search_by_status. 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_search_by_status 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