Get overview statistics about the vault: total notes, links, orphans, tags, clusters.
AI agents call get_vault_stats to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries aggregated metadata about vault structure without creating, modifying, deleting, or executing any operations. It has read-only semantics and minimal blast radius if misused by an agent—worst case it returns counts or metrics that could inform further queries but cannot directly cause harm.
From the tool's definition Tool returns statistics and overview metrics (total notes, links, orphans, tags, clusters) with no modification or execution capability. The description indicates pure observation: 'Get overview statistics about the vault.'
Attacks that exploit this kind of access
Get overview statistics about the vault: total notes, links, orphans, tags, clusters. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified 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 Modified. Nothing to install.
get_vault_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_vault_stats is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →