Add a new todo to today
AI agents use add_todo to create or update resources in Obsidian Todos MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Todos MCP Server environment.
This tool creates new task data in the vault but does not delete, execute code, move money, or trigger external operations. The effect is reversible (todos can be deleted or modified later). The blast radius of misuse is minimal—unwanted todos clutter a personal task list but cause no system damage or data loss.
From the tool's definition Tool name 'add_todo' and description 'Add a new todo to today' indicate creation of new data in the Obsidian vault. Server description confirms it 'allows users to create new todos in daily notes', which is a reversible write operation.
Attacks that exploit this kind of access
Add a new todo to today. It is categorised as a Write tool in the Obsidian Todos MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Todos MCP Server MCP server in PolicyLayer and add a rule for add_todo: 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.
add_todo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_todo 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 add_todo. 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.
add_todo 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 →