Create a new to-do item in Things.app. Add notes, tags, checklist items, and assign to projects or areas.
AI agents use add_todo to create or update resources in Things MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Things MCP Server environment.
This tool creates new task records in Things.app but the action is fully reversible—created to-do items can be deleted or edited. There is no deletion, financial impact, or code execution. The scope is limited to personal task management data with no destructive capabilities or external system effects.
From the tool's definition Tool creates a new to-do item in Things.app with notes, tags, checklist items, and project/area assignments. The verb 'Create' and 'Add' combined with data structure modifications (notes, tags, assignments) indicate reversible data creation.
Attacks that exploit this kind of access
Create a new to-do item in Things.app. Add notes, tags, checklist items, and assign to projects or areas. It is categorised as a Write tool in the Things MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Things 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 Things 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 Things MCP Server MCP server (wbopan/things-mcp). 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 →