Get cache statistics for monitoring and debugging. Returns information about file list cache, content cache, search result cache, file watcher status, inverted index, and path trie.
AI agents call get_cache_stats 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 only retrieves cache statistics for monitoring purposes. It performs no writes, deletions, code execution, or financial operations. It is a read-only diagnostic tool that queries internal state without side effects.
From the tool's definition Tool name 'get_cache_stats' and description indicate it 'Returns information about file list cache, content cache, search result cache, file watcher status, inverted index, and path trie' - purely retrieval of monitoring and debugging statistics with no…
Attacks that exploit this kind of access
Get cache statistics for monitoring and debugging. Returns information about file list cache, content cache, search result cache, file watcher status, inverted index, and path trie. 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 get_cache_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.
get_cache_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_cache_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_cache_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_cache_stats is provided by the Obsidian MCP Server MCP server (markheramis/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_cache_stats is one line of Obsidian MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →