Create a new task in the task queue. Complexity is auto-detected from title/description but can be overridden.
AI agents use task_create to create or update resources in Agent Orchestration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Orchestration environment.
This tool creates new tasks in a shared task queue used by multiple AI agents. While it is reversible (tasks can likely be deleted via task_delete or similar), it modifies shared state that other agents depend on. The risk is medium because misuse could flood the queue with spurious tasks, disrupt agent coordination, or cause agents to execute unwanted work.
From the tool's definition Tool name 'task_create' and description 'Create a new task in the task queue' indicate a write operation that creates new data in a shared coordination system.
Documented attack patterns abuse exactly the kind of access task_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Orchestration, and nothing reaches the server without passing your rules. This is the rule we recommend for task_create:
{
"version": "1",
"default": "deny",
"tools": {
"task_create": {
"limits": [
{
"counter": "task_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}task_create 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 in the task queue. Complexity is auto-detected from title/description but can be overridden. It is categorised as a Write tool in the Agent Orchestration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Orchestration MCP server in PolicyLayer and add a rule for task_create: 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 Agent Orchestration. Nothing to install.
task_create 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 task_create 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 task_create. 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.
task_create is provided by the Agent Orchestration MCP server (madebyaris/agent-orchestration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Orchestration, 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.
35 Agent Orchestration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.