tasks_create
Create a new task in your to-do list.
This record as markdown: /tools/io-github-saloprj-dialogbrain/tasks-create.md
What tasks_create does on Dialogbrain
AI agents use tasks_create to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Task title |
due_at | string | — | ISO datetime when task is due (e.g. '2026-03-31T15:00:00') |
agent_id | integer | — | Agent ID whose tasks to access. Required when calling from MCP. |
due_date | string | — | Date when task is due (e.g. '2026-03-31'). Use with due_time or alone. |
due_time | string | — | Time when task is due (e.g. '15:00'). Used with due_date. |
priority | string | — | Task priority (default: medium) |
thread_id | integer | — | Related thread ID |
description | string | — | Detailed description |
assigned_to_contact_id | integer | — | Contact ID if assigned to someone |
Parameters from the server's own tool schema.
Why tasks_create is rated Medium
This tool creates a new task, which is a reversible write operation. The task can be modified or deleted later. The scope is limited to a personal to-do list with no financial impact, external execution, or destructive potential. Severity is low because misuse would only result in unwanted task entries that are easily removable.
From the tool's definition Tool name 'tasks_create' and description 'Create a new task in your to-do list' explicitly indicate creation of data.
Attacks that exploit this kind of access
The rule that runs tasks_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tasks_create, this is the rule to start with:
tasks_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every tasks_create call is checked against it from then on.
Questions about tasks_create
Create a new task in your to-do list. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tasks_create accepts 9 parameters: title, due_at, agent_id, due_date, due_time, priority, thread_id, description, assigned_to_contact_id. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain 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 Dialogbrain. 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 Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue