// SCAN REPORT

Obsidian Dictionary MCP Server

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 29/06/2026

How to control Obsidian Dictionary MCP Server ↓

TOOL MAP

What Obsidian Dictionary MCP Server exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Obsidian Dictionary MCP Server tools

Write · Medium append_entry The tool creates new entries in a glossary file, which is a reversible write operation.

1 of Obsidian Dictionary MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Obsidian Dictionary MCP Server

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

Rate limit write operations

{
  "append_entry": {
    "limits": [
      {
        "counter": "append_entry_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_entry": {
    "limits": [
      {
        "counter": "get_entry_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 Dictionary MCP Server — 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 DICTIONARY →

Instant setup, no code required.

FULL CATALOGUE

All 4 Obsidian Dictionary MCP Server tools

WRITE 1 tools

Write append_entry Append a new glossary entry to the dictionary file. Use this to add new technical terms to the Obsidian glossa

READ 3 tools

Read get_entry Retrieve a specific entry from the glossary by term name. Returns only that entry, not the whole file. Read list_terms List all terms currently in the glossary (returns only term names, not full content). Read search_entry Check if a term already exists in the glossary. Returns true/false and the entry content if found.

FAQ

Questions about Obsidian Dictionary MCP Server

How do I prevent bulk modifications through Obsidian Dictionary MCP Server? +

The Obsidian Dictionary MCP Server server has 1 write tools including append_entry. 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 Obsidian Dictionary MCP Server.

How many tools does the Obsidian Dictionary MCP Server MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Obsidian Dictionary MCP Server? +

Register the Obsidian Dictionary MCP Server 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 Dictionary MCP Server tool call.

Deterministic rules across all 4 Obsidian Dictionary MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON OBSIDIAN DICTIONARY →

Instant setup, no code required.

4 Obsidian Dictionary MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.