get_vault_stats

THE RISK

Low Risk

Why get_vault_stats needs a policy

This tool retrieves statistical metadata about an Obsidian vault (e.g., note count, file sizes, link density). It performs a read-only query that returns aggregate information without side effects, data modification, or command execution.

From the tool's definition Tool name 'get_vault_stats' and description 'Get statistics about a vault' indicate data retrieval with no modification or execution of operations.

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

POLICY

How to control get_vault_stats

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 get_vault_stats:

policy.json

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

get_vault_stats 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 delete_note Delete a note Write render_template Render a template with variables Write add_canvas_edge Add an edge between nodes in canvas Write add_canvas_node Add a node to canvas (file, text, link, or group) Write create_canvas Create a new canvas file Write create_daily_note Create a daily note for a specific date Write create_from_template Create a new note from a template Write create_monthly_note Create a monthly note for a specific date

All 29 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 get_vault_stats

What does the get_vault_stats tool do? +

Get statistics about a 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 get_vault_stats? +

Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for get_vault_stats: 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 get_vault_stats? +

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

Can I rate-limit get_vault_stats? +

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

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

get_vault_stats is provided by the Obsidian MCP Server MCP server (bazylhorsey/obsidian-mcp-server). 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 →