// SCAN REPORT

Obsidian Vault Search for Claude

5 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 12 Jun 2026

0 can modify or destroy data

5 read-only

5 tools total

Community server · catalogue entry verified 12/06/2026

How to control Obsidian Vault Search for Claude ↓

TOOL MAP

What Obsidian Vault Search for Claude exposes to your agents

Read (5) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Obsidian Vault Search for Claude

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Vault Search for Claude, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "rg_search_backlinks": {
    "limits": [
      {
        "counter": "rg_search_backlinks_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Obsidian Vault Search for Claude — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON OBSIDIAN VAULT SEARCH FOR CLAUDE →

Free to start. No card required.

FULL CATALOGUE

All 5 Obsidian Vault Search for Claude tools

READ 5 tools

Read rg_search_backlinks rg_search_backlinks Read rg_search_links rg_search_links Read rg_search_notes rg_search_notes Read rg_search_orphaned_notes rg_search_orphaned_notes Read rg_search_recent_notes rg_search_recent_notes

FAQ

Questions about Obsidian Vault Search for Claude

Is the Obsidian Vault Search for Claude MCP server safe to use without restrictions? +

The Obsidian Vault Search for Claude server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Obsidian Vault Search for Claude MCP server expose? +

5 tools across 1 categories: Read. 5 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Obsidian Vault Search for Claude? +

Register the Obsidian Vault Search for Claude MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Obsidian Vault Search for Claude tool call.

Deterministic rules across all 5 Obsidian Vault Search for Claude tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON OBSIDIAN VAULT SEARCH FOR CLAUDE →

Free to start. No card required.

5 Obsidian Vault Search for Claude tools catalogued and risk-classified — across an index of 43,000+ MCP servers.