export_vault_archive

THE RISK

Low Risk

Why export_vault_archive needs a policy

This tool packages the entire vault into a ZIP archive, which is fundamentally a read/copy operation — it retrieves and bundles all vault data without modifying or deleting anything.

From the tool's definition Create a ZIP archive of the entire vault

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access export_vault_archive gives an agent:

POLICY

How to control export_vault_archive

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for export_vault_archive:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_vault_archive": {}
  }
}

export_vault_archive is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Obsidian MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Obsidian MCP Server tools

Destructive cleanup_broken_references Remove/fix broken links Destructive delete_attachment Remove attachment file Destructive delete_note Delete a note from the vault Execute execute_dataview_query Run Dataview DQL query and return results Write remove_tags Remove tags from an existing note Write regex_search_and_replace Find and replace with regex across vault Write add_card_to_canvas Add text/note/media card to canvas Write add_connection_to_canvas Connect cards with lines/arrows

All 120 Obsidian MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about export_vault_archive

What does the export_vault_archive tool do? +

Create a ZIP archive of the entire vault. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_vault_archive? +

Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for export_vault_archive: 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 Obsidian MCP Server. Nothing to install.

What risk level is export_vault_archive? +

export_vault_archive is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit export_vault_archive? +

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

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

export_vault_archive is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian MCP Server tool call.

Start from Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →