search_by_date_tool
A read tool on the Obsidian MCP server.
This record as markdown: /tools/adrienthebo-obsidian-mcp/search-by-date-tool.md
What search_by_date_tool does on Obsidian MCP Server
AI agents call search_by_date_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.
Why search_by_date_tool is rated Low
This tool searches notes by date, which is a query/retrieval operation with no side effects. It retrieves data from the Obsidian vault without modifying, deleting, or executing anything. The empty description lowers confidence slightly, but the tool name and context strongly suggest a read-only search operation.
From the tool's definition Tool name 'search_by_date_tool' indicates a search operation. Server description emphasizes 'reading, creating, and managing notes' and mentions 'high-performance SQLite indexing for fast searches' as a core feature.
Attacks that exploit this kind of access
The rule that runs search_by_date_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_date_tool, this is the rule to start with:
search_by_date_tool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian MCP Server, apply this rule, and every search_by_date_tool call is checked against it from then on.
Questions about search_by_date_tool
search_by_date_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.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for search_by_date_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_date_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_date_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_date_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_date_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.
More on Obsidian MCP Server, and thousands of servers like it.
This server
Across the catalogue