query_base

THE RISK

High Risk

Why query_base needs a policy

The description says 'Run a Base file', indicating this tool executes a file (likely a Dataview or similar query base file in Obsidian). Execution of arbitrary files/queries carries significant risk as an AI agent could run unintended code or queries. Categorized as Execute due to the 'run' action.

From the tool's definition "Run a Base file" — the tool explicitly runs/executes a file

Documented attack patterns abuse exactly the kind of access query_base gives an agent:

POLICY

How to control query_base

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Mcp Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for query_base:

policy.json

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

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

Create a free account and register Obsidian Mcp Pro — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Obsidian Mcp Pro tools

Destructive delete_note Delete a note. By default the file is moved to the vault Execute index_vault Build or refresh the embedding index used by Write append_to_note Append text to the end of an existing note without altering prior content. By default, ins Write prepend_to_note Insert content at the top of an existing note Write add_canvas_edge Create a directed edge connecting two existing canvas nodes. Both fromNode and toNode must Write add_canvas_node Add a new node to an Obsidian canvas and persist the updated file. Supports four node type Write create_daily_note Create a daily note for today (or a specific date) in the vault Write create_note Create a new markdown note at the given path with body content and optional YAML frontmatt

All 41 Obsidian Mcp Pro tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Obsidian Mcp Pro → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about query_base

What does the query_base tool do? +

Run a Base file. It is categorised as a Execute tool in the Obsidian Mcp Pro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query_base? +

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

What risk level is query_base? +

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

Can I rate-limit query_base? +

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

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

query_base is provided by the Obsidian Mcp Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian Mcp Pro tool call.

Start from Obsidian Mcp Pro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →