Create a new task. Args: - title (required): Task title (1-200 characters) - description (optional): Task description (up to 1000 characters) Returns: The created task with its assigned ID.
AI agents use tasks_create to create or update resources in Tasks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tasks MCP Server environment.
This tool creates new task records in a task management system. Creation of data is reversible (tasks can be deleted via tasks_delete), so it falls under Write rather than Destructive. The severity is medium because misuse could lead to database clutter or task pollution, but individual task creation poses limited blast radius compared to batch operations or data destruction.
From the tool's definition Tool name 'tasks_create' and description 'Create a new task' indicate the tool creates new data. The Args section specifies 'title (required)' and 'description (optional)' as inputs for task creation.
Attacks that exploit this kind of access
Create a new task. Args: - title (required): Task title (1-200 characters) - description (optional): Task description (up to 1000 characters) Returns: The created task with its assigned ID. It is categorised as a Write tool in the Tasks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tasks MCP Server MCP server in PolicyLayer and add a rule for tasks_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 Tasks MCP Server. Nothing to install.
tasks_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 tasks_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 tasks_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.
tasks_create is provided by the Tasks MCP Server MCP server (maxouverzou/tasks-mcp). 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 →