// SCAN REPORT

Graph Rag Obsidian

37 tools. 13 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 3 Jul 2026

13 can modify or destroy data

24 read-only

37 tools total

Community server · catalogue entry verified 03/07/2026

How to control Graph Rag Obsidian ↓

TOOL MAP

What Graph Rag Obsidian exposes to your agents

Read (24) Write / Execute (12) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Graph Rag Obsidian tools

Destructive · High clear_caches Clearing caches removes stored data (likely ChromaDB vector embeddings and graph relationship metadata) that may be expensive or impossible to reconstruct without re-indexing the entire Obsidian vault. Execute · Medium force_dspy_optimization This tool triggers an optimization process (DSPy is a framework for optimizing LLM pipelines). Execute · Medium execute_base_query The tool executes a query against the knowledge base (ChromaDB) to retrieve matching notes. Execute · High reindex_vault The tool name suggests it re-indexes the entire vault, which involves scanning files, rebuilding ChromaDB embeddings/indices, and potentially triggering Gemini API calls.

13 of Graph Rag Obsidian's 37 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Graph Rag Obsidian

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

Deny destructive operations

{
  "clear_caches": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_content_to_note": {
    "limits": [
      {
        "counter": "add_content_to_note_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "answer_question": {
    "limits": [
      {
        "counter": "answer_question_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 Graph Rag Obsidian — 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 GRAPH RAG OBSIDIAN →

Instant setup, no code required.

FULL CATALOGUE

All 37 Graph Rag Obsidian tools

DESTRUCTIVE 1 tools

Destructive clear_caches Clear specified caches or all caches if no names provided.

EXECUTE 3 tools

Execute execute_base_query Execute a base query and return matching notes. Execute force_dspy_optimization Force a DSPy optimization run if available and not already running. Execute reindex_vault reindex_vault

WRITE 9 tools

Write add_content_to_note Add content to an existing note. Write archive_note Move a note to the archive folder. Write create_base create_base Write create_folder Create a new folder in the vault. Write create_note create_note Write enrich_notes enrich_notes Write update_base Update an existing .base file configuration. Write update_note_properties Update frontmatter properties of a note. Write update_note_section update_note_section

READ 24 tools

Read answer_question answer_question Read base_from_graph base_from_graph Read check_base_exists Check if a base file exists. Read enrich_base_with_graph enrich_base_with_graph Read explore_chunk_context Get surrounding context for a specific chunk. Read get_backlinks Get all notes that link to the specified note. Read get_base_view Get formatted data for a specific base view. Read get_cache_stats Get detailed cache statistics for monitoring and optimization. Read get_dspy_optimization_status Return current DSPy optimization status and scheduling details. Read get_note_properties Get frontmatter properties of a note. Read get_notes_by_tag Get all notes that have the specified tag. Read get_related_chunks Find chunks related to a query through graph relationships. Read get_subgraph Get a subgraph containing seed notes and their neighbors. Read graph_neighbors Get neighboring notes in the graph up to specified depth. Read health_check Run registered health checks and return component status. Read list_base_files List all .base files in the vault. Read list_bases List all .base files in the vault with their metadata. Read list_notes list_notes Read read_base Read and parse a .base file by its ID. Read read_note Read the full content of a note by path. Read search_notes Basic vector search across vault chunks using ChromaDB. Read smart_search smart_search Read traverse_from_chunk Traverse the graph starting from a specific semantic chunk. Read validate_base Validate .base file content syntax and structure.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Graph Rag Obsidian

Can an AI agent delete data through the Graph Rag Obsidian MCP server? +

Yes. The Graph Rag Obsidian server exposes 1 destructive tools including clear_caches. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Graph Rag Obsidian? +

The Graph Rag Obsidian server has 9 write tools including add_content_to_note, archive_note, create_base. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Graph Rag Obsidian.

How many tools does the Graph Rag Obsidian MCP server expose? +

37 tools across 4 categories: Destructive, Execute, Read, Write. 24 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on Graph Rag Obsidian? +

Register the Graph Rag Obsidian 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 Graph Rag Obsidian tool call.

Deterministic rules across all 37 Graph Rag Obsidian tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GRAPH RAG OBSIDIAN →

Instant setup, no code required.

37 Graph Rag Obsidian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.