Creates a subtask. Create a new subtask under the provided parent task.
AI agents use createSubTask to create or update resources in Teamwork MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Teamwork MCP environment.
This tool creates new data (a subtask) in the Teamwork system. It is reversible via deletion (as evidenced by deleteTask being available on the same server), making it a Write rather than Destructive action. The blast radius is medium because creating unauthorized subtasks could clutter project management systems and consume resources, but the impact is bounded to task/project data and reversible.
From the tool's definition Tool description states 'Creates a subtask' and 'Create a new subtask under the provided parent task', which are write operations that create new data in a reversible manner.
Documented attack patterns abuse exactly the kind of access createSubTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teamwork MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for createSubTask:
{
"version": "1",
"default": "deny",
"tools": {
"createSubTask": {
"limits": [
{
"counter": "createsubtask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createSubTask 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.
Creates a subtask. Create a new subtask under the provided parent task. It is categorised as a Write tool in the Teamwork MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Teamwork MCP server in PolicyLayer and add a rule for createSubTask: 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 Teamwork MCP. Nothing to install.
createSubTask 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 createSubTask 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 createSubTask. 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.
createSubTask is provided by the Teamwork MCP server (vizioz/teamwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teamwork MCP, 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.
36 Teamwork MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.