List all due dates from tables under # Due Dates headings in Obsidian
AI agents call list_due_dates to retrieve information from Obsidian Todos MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries due date information from Obsidian notes without creating, modifying, deleting, or executing any operations. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an AI agent could only over-query or expose due date information, causing no destructive or financial harm.
From the tool's definition Tool name 'list_due_dates' and description 'List all due dates from tables under # Due Dates headings in Obsidian' indicate retrieval of existing data with no modification or deletion. The verb 'list' is a read operation.
Attacks that exploit this kind of access
List all due dates from tables under # Due Dates headings in Obsidian. It is categorised as a Read tool in the Obsidian Todos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Todos MCP Server MCP server in PolicyLayer and add a rule for list_due_dates: 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 Todos MCP Server. Nothing to install.
list_due_dates 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 list_due_dates 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 list_due_dates. 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.
list_due_dates is provided by the Obsidian Todos MCP Server MCP server (mtuckerb/obsidian-todos-mcp-server). 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 →