Permanently delete a task. This action cannot be undone.
AI agents call dida365_delete_task to permanently remove resources in Dida365 Agent — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a task) and cannot be reversed. It meets the definition of Destructive: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The high severity reflects that an AI agent with uncontrolled access could permanently destroy user tasks, losing data that may be important or unrecoverable.
From the tool's definition Tool name is 'dida365_delete_task' with description stating 'Permanently delete a task. This action cannot be undone.' The words 'Permanently delete' and 'cannot be undone' explicitly indicate irreversible data destruction.
Attacks that exploit this kind of access
Permanently delete a task. This action cannot be undone. It is categorised as a Destructive tool in the Dida365 Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dida365 Agent MCP server in PolicyLayer and add a rule for dida365_delete_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 Dida365 Agent. Nothing to install.
dida365_delete_task 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 dida365_delete_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 dida365_delete_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.
dida365_delete_task is provided by the Dida365 Agent MCP server (linhai0872/dida365-agent). 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 →