AI agents use update-todo to create or update resources in SupaThings MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SupaThings MCP environment.
The tool updates existing todo items in the Things 3 task management system. This is a reversible modification (update, not delete) of user data. While the empty description prevents full certainty, the tool name and server's stated ability to 'manage Things 3 data' combined with other write-oriented siblings (add-todo, add-project) clearly indicate data modification.
From the tool's definition Tool name 'update-todo' combined with server context showing 'manage Things 3 data' and sibling tools like 'add-todo' and 'add-project' indicate this modifies task data.
Documented attack patterns abuse exactly the kind of access update-todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SupaThings MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update-todo:
{
"version": "1",
"default": "deny",
"tools": {
"update-todo": {
"limits": [
{
"counter": "update-todo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-todo stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update-todo. It is categorised as a Write tool in the SupaThings MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SupaThings 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 SupaThings MCP. 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 SupaThings MCP server (soycanopa/supathings-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SupaThings MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 SupaThings MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.