obsidian_search_tasks
AI agents call obsidian_search_tasks to retrieve information from Mcp Apple Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search tools query and retrieve data without side effects. The naming convention aligns with read operations (search, list, get, fetch). Although the description is empty, the tool name and the Read-category operations visible in siblings (search implies no write) provide sufficient evidence. Confidence is high but slightly reduced due to missing description.
From the tool's definition Tool name 'obsidian_search_tasks' indicates a search operation. The name uses 'search', a read-only verb. No description provided, but the verb and context (sibling tools include create, delete, append, complete operations) strongly suggest this retrieves…
Attacks that exploit this kind of access
obsidian_search_tasks. It is categorised as a Read tool in the Mcp Apple Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Apple Obsidian MCP server in PolicyLayer and add a rule for obsidian_search_tasks: 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 Mcp Apple Obsidian. Nothing to install.
obsidian_search_tasks 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 obsidian_search_tasks 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 obsidian_search_tasks. 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.
obsidian_search_tasks is provided by the Mcp Apple Obsidian MCP server (rex/mcp-apple-obsidian). 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 →