更新现有的待办事项。需要提供待办事项ID和授权令牌。
AI agents use update_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.
The tool modifies existing todos by updating their properties. This is a Write operation because it creates or modifies data reversibly. It is not Destructive (no deletion), Execute (no code/command execution), Financial, or Read. Severity is medium because unauthorized todo modifications could disrupt task management, but the blast radius is limited to todo items rather than system-wide impact.
From the tool's definition Tool description states '更新现有的待办事项' (update existing todo item). This is a reversible modification operation that changes data without deleting it.
Attacks that exploit this kind of access
更新现有的待办事项。需要提供待办事项ID和授权令牌。. 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 update_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.
update_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 update_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 update_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.
update_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 →