Execute a custom Datomic query on the Roam graph beyond the available search tools.
AI agents invoke roam_datomic_query to trigger actions in Roam Research MCP Server. 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.
This tool executes arbitrary Datomic (Datalog) queries against the Roam graph. While Datomic is primarily a read-oriented query language, custom queries can be used to access any data in the graph and may support transaction functions or destructive operations depending on Roam's API exposure. The open-ended nature of 'custom' queries with no stated restrictions elevates severity.
From the tool's definition "Execute a custom Datomic query on the Roam graph" — arbitrary query execution with no stated restrictions
Documented attack patterns abuse exactly the kind of access roam_datomic_query 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_datomic_query:
{
"version": "1",
"default": "deny",
"tools": {
"roam_datomic_query": {
"limits": [
{
"counter": "roam_datomic_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Execute a custom Datomic query on the Roam graph beyond the available search tools. It is categorised as a Execute tool in the Roam Research MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Roam Research MCP Server 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 MCP Server. 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 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.