get_vault_stats

Return a quick health snapshot of the vault: note count, total bytes, total words, unique tag count, untagged-note count, and the most-recently-modified note. Useful for dashboards and

ServerObsidian Mcp Pro
CategoryRead

How to control get_vault_stats ↓

WHAT IT DOES

What get_vault_stats does on Obsidian Mcp Pro

AI agents call get_vault_stats to retrieve information from Obsidian Mcp Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_vault_stats needs a policy

get_vault_stats purely retrieves aggregate metadata about the vault without any side effects, reversible changes, or external operations. It is a passive query operation suitable for dashboards and monitoring, with minimal blast radius even if misused.

From the tool's definition Tool returns read-only statistics: 'note count, total bytes, total words, unique tag count, untagged-note count, and the most-recently-modified note.' No creation, modification, deletion, or execution capabilities.

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 Pro, 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 Pro — 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 Pro tools

Destructive delete_note Delete a note. By default the file is moved to the vault Execute index_vault Build or refresh the embedding index used by Execute query_base Run a Base file Write append_to_note Append text to the end of an existing note without altering prior content. By default, ins Write prepend_to_note Insert content at the top of an existing note Write add_canvas_edge Create a directed edge connecting two existing canvas nodes. Both fromNode and toNode must Write add_canvas_node Add a new node to an Obsidian canvas and persist the updated file. Supports four node type Write create_daily_note Create a daily note for today (or a specific date) in the vault

All 41 Obsidian Mcp Pro 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? +

Return a quick health snapshot of the vault: note count, total bytes, total words, unique tag count, untagged-note count, and the most-recently-modified note. Useful for dashboards and. It is categorised as a Read tool in the Obsidian Mcp Pro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_vault_stats? +

Register the Obsidian Mcp Pro 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 Pro. 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 Pro MCP server (rps321321/obsidian-mcp-pro). 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 Pro tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.