Decomposes an existing complex task into smaller, more manageable subtasks. All tasks with complexity higher than low must always be decomposed before execution. Tasks MUST be in todo status to be decomposed. Subtasks with the same sequence order may be executed in parallel. Subtasks should inclu...
AI agents use decompose_task to create or update resources in Mcp Task Manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Task Manager environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
taskID | string | Yes | The task to decompose |
subtasks | array | Yes | Array of smaller, manageable subtasks to create |
decompositionReason | string | Yes | The reason for decomposing this task |
Parameters from the server's own tool schema.
This tool modifies the task structure by creating new subtasks linked to an existing task. It is a Write operation because it creates new data entries (subtasks) reversibly—subtasks can be deleted or modified later. It does not execute external operations (Execute), delete data irreversibly (Destructive), move money (Financial), or simply retrieve information (Read).
From the tool's definition The tool 'decomposes an existing complex task into smaller, more manageable subtasks' and 'Created subtasks may be decomposed later if needed', indicating it creates new task records (subtasks) within the system.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
Decomposes an existing complex task into smaller, more manageable subtasks. All tasks with complexity higher than low must always be decomposed before execution. Tasks MUST be in todo status to be decomposed. Subtasks with the same sequence order may be executed in parallel. Subtasks should include a verification subtask. Created subtasks may be decomposed later if needed. It is categorised as a Write tool in the Mcp Task Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
decompose_task accepts 3 parameters: taskID, subtasks, decompositionReason. Required: taskID, subtasks, decompositionReason. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Task Manager MCP server in PolicyLayer and add a rule for decompose_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 Mcp Task Manager. Nothing to install.
decompose_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 decompose_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 decompose_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.
decompose_task is provided by the Mcp Task Manager MCP server (@blizzy/mcp-task-manager). 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 →