reindex_vault · Graph Rag Obsidian MCP: Risk & Policy

WHAT IT DOES

What reindex_vault does on Graph Rag Obsidian

AI agents invoke reindex_vault 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 reindex_vault needs a policy

The tool name suggests it re-indexes the entire vault, which involves scanning files, rebuilding ChromaDB embeddings/indices, and potentially triggering Gemini API calls. This is an Execute-level operation with potential high blast radius (full vault reprocessing, API costs, cache invalidation). Confidence is lowered due to empty description.

From the tool's definition Tool name 'reindex_vault' and empty description; inferred from server context involving ChromaDB indexing of Obsidian vault

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reindex_vault Rate-limited

reindex_vault 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": {
    "reindex_vault": {
      "limits": [
        {
          "counter": "reindex_vault_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 reindex_vault

What does the reindex_vault tool do? +

reindex_vault. 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 reindex_vault? +

Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for reindex_vault: 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 reindex_vault? +

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

Can I rate-limit reindex_vault? +

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

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

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