Critical Risk →

clear_task

Clears the current task data.

How to control clear_task ↓

What clear_task does on Divide and Conquer MCP Server

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

Critical Risk

Why clear_task needs a policy

The tool permanently removes task data without a reversible operation or undo capability visible in the sibling tools (which support add, mark, and reorder operations but no recovery mechanism). This fits the Destructive category as it overwrites/deletes data that cannot be restored. Severity is high because an agent miscall could lose all work on a complex multi-step task decomposition.

From the tool's definition Tool name 'clear_task' with description 'Clears the current task data.' indicates irreversible deletion of task state, including potentially complex task decompositions, context, and progress tracking that cannot be recovered.

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

How to control clear_task

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_task"
  ]
}

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

  1. Create a free account and register Divide and Conquer MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about clear_task

What does the clear_task tool do? +

Clears the current task data. It is categorised as a Destructive tool in the Divide and Conquer 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 clear_task? +

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

What risk level is clear_task? +

clear_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 clear_task? +

Yes. Add a rate_limit block to the clear_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 clear_task completely? +

Set action: deny in the PolicyLayer policy for clear_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 clear_task? +

clear_task is provided by the Divide and Conquer MCP Server MCP server (landicefu/divide-and-conquer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Divide and Conquer MCP Server tool call.

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

Free to start. No card required.

15 Divide and Conquer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.