manage_task_list
Manage the workspace task list. Add, update, complete, delete, or list tasks.
This record as markdown: /tools/io-github-homenshum-nodebench/manage-task-list.md
What manage_task_list does on Nodebench
AI agents use manage_task_list to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.
Why manage_task_list is rated Medium
Although the description includes 'delete,' task list management typically operates on non-critical, recoverable data within a workspace context. The tool's main purpose is data manipulation (create/modify/remove tasks) rather than irreversible destruction of core resources. An AI agent misusing this could remove user tasks but cannot destroy external systems or critical data.
From the tool's definition Tool description states it can 'Add, update, complete, delete, or list tasks.' The operations 'add, update, complete' are reversible Write operations, while 'delete' is destructive.
Attacks that exploit this kind of access
The rule that runs manage_task_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_task_list, this is the rule to start with:
manage_task_list 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 Nodebench, apply this rule, and every manage_task_list call is checked against it from then on.
Questions about manage_task_list
Manage the workspace task list. Add, update, complete, delete, or list tasks. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodebench MCP server in PolicyLayer and add a rule for manage_task_list: 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 Nodebench. Nothing to install.
manage_task_list 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 manage_task_list 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 manage_task_list. 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.
manage_task_list is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue