dataview_query · Connect MCP: Risk & Policy

WHAT IT DOES

What dataview_query does on Connect MCP

AI agents invoke dataview_query to trigger actions in Connect MCP. 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 IT NEEDS A POLICY

Why dataview_query needs a policy

This tool executes arbitrary Dataview Query Language (DQL) queries against the vault. While DQL is primarily read-oriented, executing arbitrary query language against a data store classifies as Execute rather than Read, as the query engine interprets and runs code/expressions.

From the tool's definition Query notes using Dataview DQL... Supports LIST, TABLE, TASK queries

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dataview_query Rate-limited

dataview_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dataview_query": {
      "limits": [
        {
          "counter": "dataview_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Connect MCP, so you can run agents against it safely.

FAQ

Questions about dataview_query

What does the dataview_query tool do? +

Query notes using Dataview DQL. PREFERRED for finding notes by frontmatter fields, tags, folders, or dates. Supports LIST, TABLE, TASK queries. Use vault_search only for full-text content search. It is categorised as a Execute tool in the Connect MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dataview_query? +

Register the Connect MCP server in PolicyLayer and add a rule for dataview_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 Connect MCP. Nothing to install.

What risk level is dataview_query? +

dataview_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dataview_query? +

Yes. Add a rate_limit block to the dataview_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.

How do I block dataview_query completely? +

Set action: deny in the PolicyLayer policy for dataview_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.

What MCP server provides dataview_query? +

dataview_query is provided by the Connect MCP server (joch/obsidian-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.