search_by_property_tool
AI agents call search_by_property_tool 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.
The tool name strongly suggests a search/query operation that retrieves data based on property filters. No description was provided, which lowers confidence slightly, but the naming convention and context of sibling tools (which are predominantly read or write operations for explicit modifications) indicate this is a read operation with no side effects. Searching does not modify vault state.
From the tool's definition Tool name 'search_by_property_tool' indicates a search operation. In the context of an Obsidian vault management server, this aligns with querying notes by properties—a read-only operation.
Attacks that exploit this kind of access
search_by_property_tool. 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 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.
search_by_property_tool 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 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.
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.
search_by_property_tool is provided by the Obsidian MCP Server MCP server (suhailnajeeb/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →