create_subtask
Create a child task under a parent task so an Agent can decompose work. The child inherits the parent\
This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/create-subtask.md
What create_subtask does on Todo for AI MCP Server
AI agents use create_subtask to create or update resources in Todo for AI MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo for AI MCP Server environment.
Why create_subtask is rated Medium
An AI agent can call create_subtask faster than any human can review: one bad instruction and it creates or modifies resources in Todo for AI MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_subtask safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_subtask, this is the rule to start with:
create_subtask 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 Todo for AI MCP Server, apply this rule, and every create_subtask call is checked against it from then on.
Questions about create_subtask
Create a child task under a parent task so an Agent can decompose work. The child inherits the parent\. It is categorised as a Write tool in the Todo for AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for create_subtask: 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 Todo for AI MCP Server. Nothing to install.
create_subtask 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_subtask 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_subtask. 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_subtask is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todo for AI MCP Server, and thousands of servers like it.
This server
Across the catalogue