tasks_delete
Delete a task from your to-do list by its ID.
This record as markdown: /tools/io-github-saloprj-dialogbrain/tasks-delete.md
What tasks_delete does on Dialogbrain
AI agents call tasks_delete to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
task_id | integer | Yes | ID of the task to delete |
agent_id | integer | — | Agent ID whose task to delete. Required when calling from MCP. |
Parameters from the server's own tool schema.
Why tasks_delete is rated Critical
The tool performs an irreversible deletion operation on user data (tasks). Deletion cannot be undone and results in permanent data loss. This qualifies as Destructive rather than Write. Severity is high because unintended deletion of tasks could disrupt user workflows, though the blast radius is limited to task data rather than critical systems or financial operations.
From the tool's definition Tool name includes 'delete' and description states 'Delete a task from your to-do list by its ID' — this irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs tasks_delete 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_delete, this is the rule to start with:
tasks_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every tasks_delete call is checked against it from then on.
Questions about tasks_delete
Delete a task from your to-do list by its ID. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
tasks_delete accepts 2 parameters: task_id, agent_id. Required: task_id. 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_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tasks_delete 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_delete. 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_delete 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.
Across the catalogue