创建新的待办事项。支持标题、备注、标签、清单、截止日期等。
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.
Creating a todo is a Write operation—it modifies the Things 3 database by adding a new item, but the action is fully reversible (the todo can be deleted). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. Severity is low because the blast radius of an AI agent creating unwanted todos is minimal and easily remedied.
From the tool's definition Tool name 'add_todo' and description '创建新的待办事项' (create new todo item) indicate creation of reversible data. The supported parameters (title, notes, tags, checklist, deadline) are additive modifications to task management data.
Attacks that exploit this kind of access
创建新的待办事项。支持标题、备注、标签、清单、截止日期等。. 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 (mieluoxxx/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 →