Low Risk

search_notes_metadata

MCP Tool: Searches the metadata of all notes for a query string.

How to control search_notes_metadata ↓

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

Low Risk

This tool only retrieves and queries note metadata without side effects. It does not create, modify, delete, or execute any operations. While it operates within a user's Obsidian vault (which may contain sensitive information), the tool itself performs no destructive or dangerous actions. The severity is low because misuse results in information disclosure rather than data loss or system compromise.

From the tool's definition Tool description states it 'Searches the metadata of all notes for a query string' — a pure retrieval operation with no data modification, deletion, or execution. The verb 'searches' and the context of querying metadata indicate read-only access.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Tool Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_notes_metadata:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_notes_metadata": {}
  }
}

search_notes_metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Obsidian MCP Tool Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_notes_metadata tool do? +

MCP Tool: Searches the metadata of all notes for a query string. It is categorised as a Read tool in the Obsidian MCP Tool Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_notes_metadata? +

Register the Obsidian MCP Tool Server MCP server in PolicyLayer and add a rule for search_notes_metadata: 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 Tool Server. Nothing to install.

What risk level is search_notes_metadata? +

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

Can I rate-limit search_notes_metadata? +

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

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

search_notes_metadata is provided by the Obsidian MCP Tool Server MCP server (rwb3n/obsidian-mcp). 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 Tool Server tool call.

Deterministic rules across all 18 Obsidian MCP Tool Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Obsidian MCP Tool Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.