count_entries

THE RISK

Low Risk

Why count_entries needs a policy

This tool performs a read-only operation that returns statistics about vault contents. It has no side effects, does not modify data, and does not execute code or trigger external operations. The minimal blast radius (returning a count) and read-only nature place it firmly in the Read category with low severity.

From the tool's definition Tool name is 'count_entries' and description states it 'Counts the number of indexed notes and chunks in your Obsidian Vault' — a pure query operation that retrieves metadata without modifying any data.

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

POLICY

How to control count_entries

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

policy.json

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

count_entries 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_file Deletes a file within your Obsidian Vault. Provide the Destructive delete_folder Deletes a folder within your Obsidian Vault. Provide the Write create_file Creates a new file with the specified content at the given path within your Obsidian Vault Write create_folder Creates a folder within your Obsidian Vault. Provide the Write create_link Creates an Obsidian wikilink from one note to another (e.g., Write edit_file Edits a specific range of lines within a file in your Obsidian Vault. Replaces the content Read list_files Lists files and sub-folders within a specified directory of your Obsidian Vault. Use Read read_file Reads the full content of a specific note or file within your Obsidian Vault. Provide the

All 10 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 count_entries

What does the count_entries tool do? +

Counts the number of indexed notes and chunks in your Obsidian 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 count_entries? +

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

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

Can I rate-limit count_entries? +

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

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

count_entries is provided by the Obsidian MCP Server MCP server (minhao-zhang/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 →