palace_dataview · Obsidian Palace MCP: Risk & Policy

WHAT IT DOES

What palace_dataview does on Obsidian Palace MCP

AI agents invoke palace_dataview to trigger actions in Obsidian Palace 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 palace_dataview needs a policy

This tool executes a query language (Dataview QL) against stored data. While Dataview queries are typically read-only operations, the Execute category applies because: (1) the tool explicitly uses the word "Execute", (2) running arbitrary queries can have side effects depending on the vault state and query content, (3) it provides programmatic access to vault data via an external language, and (4) the blast radius…

From the tool's definition Tool is explicitly described as "Execute Dataview Query Language (DQL) queries against notes" with support for TABLE queries that read and filter data from the vault.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

palace_dataview Rate-limited

palace_dataview 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": {
    "palace_dataview": {
      "limits": [
        {
          "counter": "palace_dataview_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 Obsidian Palace MCP, so you can run agents against it safely.

FAQ

Questions about palace_dataview

What does the palace_dataview tool do? +

Execute Dataview Query Language (DQL) queries against notes. Supports: - TABLE queries: TABLE field1, field2 FROM. It is categorised as a Execute tool in the Obsidian Palace 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 palace_dataview? +

Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_dataview: 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 Palace MCP. Nothing to install.

What risk level is palace_dataview? +

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

Can I rate-limit palace_dataview? +

Yes. Add a rate_limit block to the palace_dataview 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 palace_dataview completely? +

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

palace_dataview is provided by the Obsidian Palace MCP server (probably-computers/obsidian-palace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.