// MCP TOOL REFERENCE

delete_task

Permanently delete a cloud task. This action cannot be undone and all conversation history will be lost. Use this to clean up tasks you no longer need. Usage Example: \

ServerCloud Agent MCP Server
CategoryDestructive

How to control delete_task ↓

WHAT IT DOES

What delete_task does on Cloud Agent MCP Server

AI agents call delete_task to permanently remove resources in Cloud Agent MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why delete_task needs a policy

This tool irreversibly deletes data (tasks and associated conversation history) with no recovery mechanism. While the blast radius is somewhat limited to a single task rather than an entire system, the permanent nature and data loss make this Destructive rather than Write. High severity reflects that an agent misusing this could lose important work and collaboration history.

From the tool's definition Tool description explicitly states: 'Permanently delete a cloud task. This action cannot be undone and all conversation history will be lost.' The use of 'Permanently delete' and 'cannot be undone' are definitive markers of destructive operations.

Documented attack patterns abuse exactly the kind of access delete_task gives an agent:

POLICY

How to control delete_task

PolicyLayer is an MCP gateway — it sits between your AI agents and Cloud Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_task:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_task"
  ]
}

delete_task disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Cloud Agent MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cloud Agent MCP Server tools

Execute add_followup Send additional instructions to a RUNNING task. Use this to guide the task, request change Execute create_task Launch a new cloud task to work on a repository. Requires a repository URL and task prompt Read get_conversation Get the complete conversation history of a task including the original prompt, all follow- Read get_me Get API key information including name, creation date, and user email. Use this to verify Read get_models List all available LLM models for cloud tasks. If you omit the model parameter in \ Read get_repos Get available repositories. First checks if you are in a git directory and returns that re Read get_task Get the current status and full details of a specific cloud task. Returns comprehensive in Read list_tasks List all cloud tasks for the authenticated user. Returns comprehensive information includi

All 9 Cloud Agent MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Cloud Agent MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_task

What does the delete_task tool do? +

Permanently delete a cloud task. This action cannot be undone and all conversation history will be lost. Use this to clean up tasks you no longer need. Usage Example: \. It is categorised as a Destructive tool in the Cloud Agent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_task? +

Register the Cloud Agent MCP Server MCP server in PolicyLayer and add a rule for 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 Cloud Agent MCP Server. Nothing to install.

What risk level is delete_task? +

delete_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_task? +

Yes. Add a rate_limit block to the 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.

How do I block delete_task completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides delete_task? +

delete_task is provided by the Cloud Agent MCP Server MCP server (jxnl/cursor-cloud-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cloud Agent MCP Server tool call.

Start from Cloud Agent MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

9 Cloud Agent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.