search_by_property_tool

A read tool on the Obsidian MCP server.

SERVERObsidian MCP Server SOURCEadrienthebo/obsidian-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrienthebo-obsidian-mcp/search-by-property-tool.md

WHAT IT DOES

What search_by_property_tool does on Obsidian MCP Server

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

RISK

Why search_by_property_tool is rated Low

The tool name and context suggest it searches or filters notes by properties without modifying data. Search and query operations are classified as Read category with low severity, as they retrieve information without side effects. Confidence is high despite empty description due to clear naming convention and server architecture context.

From the tool's definition Tool name 'search_by_property_tool' indicates a search operation that queries data. The server description emphasizes 'reading' and 'SQLite indexing for fast searches,' and this tool fits the search/query pattern.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_by_property_tool safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_by_property_tool, this is the rule to start with:

search_by_property_tool Allowed

search_by_property_tool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian MCP Server, apply this rule, and every search_by_property_tool call is checked against it from then on.

FAQ

Questions about search_by_property_tool

What does the search_by_property_tool tool do? +

search_by_property_tool is a read tool on the Obsidian MCP Server MCP server. 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 search_by_property_tool? +

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

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

Can I rate-limit search_by_property_tool? +

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

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

search_by_property_tool is provided by the Obsidian MCP Server MCP server (adrienthebo/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Obsidian MCP Server, and thousands of servers like it.

This server

All 27 Obsidian MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →