execute a dataview query language (dql) query. dql is a powerful, sql-like language for querying obsidian notes based on metadata (frontmatter, inline fields), tags, folders, links, file properties (name, path, dates), and tasks. use it to filter, sort, group, and transform data from your obsidia...
AI agents invoke obsidian_dataview_search to trigger actions in Obsidian 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.
The tool executes arbitrary DQL queries, which is an active execution of a query language (SQL-like) against the vault. While the server description says it is read-oriented (search, read, analyze), executing an arbitrary query language with filtering, sorting, grouping, and transformation capabilities is categorized as Execute.
From the tool's definition "execute a dataview query language (dql) query" — the tool runs arbitrary DQL queries against the Obsidian vault
Documented attack patterns abuse exactly the kind of access obsidian_dataview_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian_dataview_search:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian_dataview_search": {
"limits": [
{
"counter": "obsidian_dataview_search_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}obsidian_dataview_search 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 dataview query language (dql) query. dql is a powerful, sql-like language for querying obsidian notes based on metadata (frontmatter, inline fields), tags, folders, links, file properties (name, path, dates), and tasks. use it to filter, sort, group, and transform data from your obsidian vault. key difference from sql: dql executes queries sequentially, line by line, passing results between commands. this allows multiple. It is categorised as a Execute tool in the Obsidian MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for obsidian_dataview_search: 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 Obsidian MCP Server. Nothing to install.
obsidian_dataview_search 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 obsidian_dataview_search 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 obsidian_dataview_search. 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.
obsidian_dataview_search is provided by the Obsidian MCP Server MCP server (louis030195/easy-obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian 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.
6 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.