AI agents call analyze_vault_health to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve and compute aggregate health metrics about a vault—no creation, modification, deletion, or external execution involved. It produces information about vault state for diagnostic purposes. The context of sibling tools (many Write and Execute operations) confirms this is a reporting/inspection function rather than an action tool.
From the tool's definition Tool name 'analyze_vault_health' and description 'Overall vault statistics/issues' indicate retrieval and analysis of vault metadata without modification. The word 'analyze' and 'statistics' are consistent with diagnostic Read operations.
Documented attack patterns abuse exactly the kind of access analyze_vault_health gives an agent:
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 analyze_vault_health:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_vault_health": {}
}
}analyze_vault_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Overall vault statistics/issues. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for analyze_vault_health: 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.
analyze_vault_health 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 analyze_vault_health 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 analyze_vault_health. 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.
analyze_vault_health 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.
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.
Free to start. No card required.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.