roam_datomic_query
Execute a custom Datomic query on the Roam graph for advanced data retrieval beyond the available search tools. This provides direct access to Roam\
This record as markdown: /tools/2b3pro-roam-research-mcp/roam-datomic-query.md
What roam_datomic_query does on Roam Research
AI agents invoke roam_datomic_query to trigger actions in Roam Research. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why roam_datomic_query is rated High
This tool executes arbitrary Datomic queries directly against the Roam graph database. While described as 'data retrieval,' executing custom queries with direct database access could include destructive operations (e.g., retractions in Datomic). The 'custom query' and 'direct access' nature elevates severity since an AI agent could craft queries with unintended side effects.
From the tool's definition "Execute a custom Datomic query on the Roam graph" and "provides direct access to Roam"
Attacks that exploit this kind of access
The rule that runs roam_datomic_query 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_datomic_query, this is the rule to start with:
roam_datomic_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_datomic_query call is checked against it from then on.
Questions about roam_datomic_query
Execute a custom Datomic query on the Roam graph for advanced data retrieval beyond the available search tools. This provides direct access to Roam\. It is categorised as a Execute tool in the Roam Research MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Roam Research MCP server in PolicyLayer and add a rule for roam_datomic_query: 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_datomic_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the roam_datomic_query 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_datomic_query. 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_datomic_query 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.
Across the catalogue