createTask
Create a new task with optional parent and index positioning.\n\n
This record as markdown: /tools/108yen-task-orchestrator-mcp/createtask.md
What createTask does on Task Orchestrator
AI agents use createTask to create or update resources in Task Orchestrator, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Task Orchestrator environment.
Why createTask is rated Medium
This tool creates new data structures (tasks) in a reversible manner. It does not execute arbitrary code, delete data, or handle financial transactions. The severity is medium because task creation could potentially be abused to spam or pollute a task system, but the impact is limited to data creation without external execution or destruction. Confidence is high given the explicit 'Create' verb in the description.
From the tool's definition Tool name 'createTask' combined with description 'Create a new task' indicates data creation. The optional parameters for 'parent and index positioning' show it modifies task hierarchy/state.
Attacks that exploit this kind of access
The rule that runs createTask safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Task Orchestrator, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createTask, this is the rule to start with:
createTask 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 Task Orchestrator, apply this rule, and every createTask call is checked against it from then on.
Questions about createTask
Create a new task with optional parent and index positioning.\n\n. It is categorised as a Write tool in the Task Orchestrator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Task Orchestrator MCP server in PolicyLayer and add a rule for createTask: 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 Task Orchestrator. Nothing to install.
createTask 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 createTask 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 createTask. 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.
createTask is provided by the Task Orchestrator MCP server (108yen/task-orchestrator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Task Orchestrator, and thousands of servers like it.
This server
Across the catalogue