Create a new task. Pass parent_id to create a child of an existing task. Omit parent_id only when creating the very first root task on an empty tree. Decompose work into sub-tasks before starting it — not after problems arise. For sequential work, create all sibling tasks upfront with depends_on ...
AI agents use create_task to create or update resources in Conductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Conductor environment.
The tool creates and modifies data structures (tasks) in a persistent system but the operation is reversible—tasks can presumably be archived or deleted. It doesn't execute external code or trigger irreversible destructive actions. While misuse could cause organizational chaos in task planning, the impact is bounded by the task management domain and doesn't affect production systems or data integrity.
From the tool's definition Tool explicitly creates new tasks in a persistent hierarchical task tree. Description states 'Create a new task' and allows passing parent_id to establish task relationships. This is a reversible data creation operation.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access create_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for create_task:
{
"version": "1",
"default": "deny",
"tools": {
"create_task": {
"limits": [
{
"counter": "create_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_task 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.
Create a new task. Pass parent_id to create a child of an existing task. Omit parent_id only when creating the very first root task on an empty tree. Decompose work into sub-tasks before starting it — not after problems arise. For sequential work, create all sibling tasks upfront with depends_on and status=. It is categorised as a Write tool in the Conductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conductor MCP server in PolicyLayer and add a rule for create_task: 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 Conductor. Nothing to install.
create_task 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 create_task 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 create_task. 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.
create_task is provided by the Conductor MCP server (shannonbay/conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Conductor, 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.
16 Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.