Add multiple new tasks to the active checklist. Tasks are appended to the end of the list and automatically assigned new IDs.
AI agents use add_tasks to create or update resources in Subconductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Subconductor environment.
This tool creates new checklist task entries, which is a reversible write operation. The tasks can be removed (via remove_task) and the checklist can be archived, making this a Write rather than Destructive action. It has low severity because task list modifications have minimal blast radius in a workflow management context—no external systems are affected, no data is deleted, and mistakes can be easily corrected.
From the tool's definition Tool description states it 'Add[s] multiple new tasks to the active checklist' and 'Tasks are appended to the end of the list', indicating creation of new data structures within the checklist system.
Attacks that exploit this kind of access
Add multiple new tasks to the active checklist. Tasks are appended to the end of the list and automatically assigned new IDs. It is categorised as a Write tool in the Subconductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Subconductor MCP server in PolicyLayer and add a rule for add_tasks: 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 Subconductor. Nothing to install.
add_tasks 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 add_tasks 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 add_tasks. 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.
add_tasks is provided by the Subconductor MCP server (paulbenchea/mcp-subconductor). 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 →