List tasks from a specific note, folder, or the entire vault. Filter by status.
AI agents call tasks_list to retrieve information from Mcp Obsidian Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only querying of task data. It retrieves and lists tasks with optional filtering by status, which are characteristic Read operations. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could retrieve task information unnecessarily, but cannot harm the vault or cause side effects.
From the tool's definition Tool name 'tasks_list' and description 'List tasks from a specific note, folder, or the entire vault. Filter by status' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List tasks from a specific note, folder, or the entire vault. Filter by status. It is categorised as a Read tool in the Mcp Obsidian Planner MCP Server, which means it retrieves data without modifying state.
Register the Mcp Obsidian Planner MCP server in PolicyLayer and add a rule for tasks_list: 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 Obsidian Planner. Nothing to install.
tasks_list 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 tasks_list 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 tasks_list. 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.
tasks_list is provided by the Mcp Obsidian Planner MCP server (jarero321/mcp-obsidian-planner). 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 →