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.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about task_list_update

What does the task_list_update tool do? +

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.

How do I enforce a policy on task_list_update? +

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.

What risk level is task_list_update? +

task_list_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit task_list_update? +

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.

How do I block task_list_update completely? +

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.

What MCP server provides task_list_update? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CoWork OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.