task_list_update
Replace the full ordered session checklist state. Existing items keep their ids when supplied; new items may omit id and the runtime will generate one.
This record as markdown: /tools/cowork-os/task-list-update.md
What task_list_update does on CoWork OS
AI agents use task_list_update to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why task_list_update is rated Medium
This tool overwrites/replaces the session task list state with new content. It modifies data (the checklist) reversibly — items are updated or created, not permanently deleted. This is a Write operation. Misuse could disrupt task tracking or inject malicious tasks into an agent's session, giving it medium severity.
From the tool's definition Replace the full ordered session checklist state. Existing items keep their ids when supplied; new items may omit id and the runtime will generate one.
Attacks that exploit this kind of access
The rule that runs task_list_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For task_list_update, this is the rule to start with:
task_list_update 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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every task_list_update call is checked against it from then on.
Questions about task_list_update
Replace the full ordered session checklist state. Existing items keep their ids when supplied; new items may omit id and the runtime will generate one. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for task_list_update: 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 CoWork OS. Nothing to install.
task_list_update 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 task_list_update 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 task_list_update. 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.
task_list_update is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue