// SCAN REPORT

Mcp Markdown Vault

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

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

Last updated: 12 Jun 2026

4 can modify or destroy data

1 read-only

5 tools total

Community server · catalogue entry verified 12/06/2026

How to control Mcp Markdown Vault ↓

TOOL MAP

What Mcp Markdown Vault exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mcp Markdown Vault tools

Destructive · High vault Although this tool includes Read operations (list, read, stat) and Write operations (create, update, create_from_template), the presence of 'delete' capability for whole-file removal places it in the Destructive category Execute · Medium system The tool performs system administration operations including triggering async reindex rebuilds and persisting overview data. Write · Medium workflow The tool manages workflow state including transitions and resets. Write · High edit Although the tool description mentions 'delete' and 'replace' operations that could be considered destructive, the overall design emphasizes safety mechanisms (dryRun previews, AST-based surgical editing, batch operation

4 of Mcp Markdown Vault's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mcp Markdown Vault

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

Deny destructive operations

{
  "vault": {
    "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

{
  "workflow": {
    "limits": [
      {
        "counter": "workflow_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "view": {
    "limits": [
      {
        "counter": "view_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 Mcp Markdown Vault — 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 MCP MARKDOWN VAULT →

Free to start. No card required.

FULL CATALOGUE

All 5 Mcp Markdown Vault tools

DESTRUCTIVE 1 tools

Destructive vault Manage vault notes. Vault scope: ${vaultScope}. Actions: list (browse notes), read (full note), create/update/

EXECUTE 1 tools

Execute system System administration for this vault (${vaultScope}). Actions: status (indexing/backlinks/workflow health), re

WRITE 2 tools

Write workflow Manage optional agent workflow state for this vault (${vaultScope}): status, transition, history, reset. Typic Write edit Edit notes safely. Vault scope: ${vaultScope}. Supports AST edits by heading/block ID, freeform line/string re

READ 1 tools

Read view Read and search markdown notes. Vault scope: ${vaultScope}.\nActions: search (heading-aware fragment retrieval

EXPLORE

Related servers

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

FAQ

Questions about Mcp Markdown Vault

Can an AI agent delete data through the Mcp Markdown Vault MCP server? +

Yes. The Mcp Markdown Vault server exposes 1 destructive tools including vault. 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 Mcp Markdown Vault? +

The Mcp Markdown Vault server has 2 write tools including workflow, edit. 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 Mcp Markdown Vault.

How many tools does the Mcp Markdown Vault MCP server expose? +

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

How do I enforce a policy on Mcp Markdown Vault? +

Register the Mcp Markdown Vault 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 Mcp Markdown Vault tool call.

Deterministic rules across all 5 Mcp Markdown Vault tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP MARKDOWN VAULT →

Free to start. No card required.

5 Mcp Markdown Vault tools catalogued and risk-classified — across an index of 43,000+ MCP servers.