Create a new task with all required fields (title, description, status, dependencies, exit_criteria, priority, notes) and optional fields (research_notes, action_plan, execution_notes, agent_instructions_template, tags)
AI agents use create_task to create or update resources in TasksMultiServer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TasksMultiServer environment.
The tool creates new task records with multiple fields (title, description, status, dependencies, exit_criteria, priority, notes, and optional fields). This is a Write operation—it adds data to the system reversibly.
From the tool's definition Tool name is 'create_task' and description states it 'Create a new task' with fields that can be populated. This is a creation operation that generates new data in a reversible manner.
Attacks that exploit this kind of access
Create a new task with all required fields (title, description, status, dependencies, exit_criteria, priority, notes) and optional fields (research_notes, action_plan, execution_notes, agent_instructions_template, tags). It is categorised as a Write tool in the TasksMultiServer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TasksMultiServer MCP server in PolicyLayer and add a rule for create_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 TasksMultiServer. Nothing to install.
create_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 create_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 create_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.
create_task is provided by the TasksMultiServer MCP server (keyurgolani/tasksmultiserver). 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 →