execute_base_query · Graph Rag Obsidian MCP: Risk & Policy

WHAT IT DOES

What execute_base_query does on Graph Rag Obsidian

AI agents invoke execute_base_query to trigger actions in Graph Rag Obsidian. 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 execute_base_query needs a policy

The tool executes a query against the knowledge base (ChromaDB) to retrieve matching notes. While the primary result is reading/returning data, the 'execute' semantics and arbitrary query execution warrant the Execute category over plain Read. Misuse could expose unintended data or trigger unexpected backend operations, giving it medium severity.

From the tool's definition 'Execute a base query and return matching notes' — the word 'Execute' in both the tool name and description indicates running a query operation against the ChromaDB base.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_base_query Rate-limited

execute_base_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": {
    "execute_base_query": {
      "limits": [
        {
          "counter": "execute_base_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 Graph Rag Obsidian, so you can run agents against it safely.

FAQ

Questions about execute_base_query

What does the execute_base_query tool do? +

Execute a base query and return matching notes. It is categorised as a Execute tool in the Graph Rag Obsidian MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_base_query? +

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

What risk level is execute_base_query? +

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

Can I rate-limit execute_base_query? +

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

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

execute_base_query is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.