AI agents call roam_search_by_status to retrieve information from Roam Research MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations that retrieve data based on status filters are Read category operations. They query existing data without side effects. The tool description is empty, which slightly reduces confidence, but the naming convention and sibling tool patterns provide sufficient evidence that this is a retrieval/search function rather than a write, execute, or destructive operation.
From the tool's definition Tool name 'roam_search_by_status' indicates a search operation. The sibling tools on this server include clear Read operations (fetch_pdf_content, get_roam_graph_info, parse_url) and Write operations (roam_add_todo, roam_create_block, roam_create_page).
Documented attack patterns abuse exactly the kind of access roam_search_by_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Roam Research MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for roam_search_by_status:
{
"version": "1",
"default": "deny",
"tools": {
"roam_search_by_status": {}
}
}roam_search_by_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
roam_search_by_status. It is categorised as a Read tool in the Roam Research MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Roam Research MCP Server 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 MCP Server. 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 MCP server (philosolares/roam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Roam Research MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 Roam Research MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.