# deleteTask

Delete a task by its ID

Agent View of the PolicyLayer registry record for `deleteTask`. HTML page: https://policylayer.com/tools/108yen-task-orchestrator-mcp/deletetask

## Facts

- Tool: `deleteTask`
- Server: Task Orchestrator (`108yen/task-orchestrator-mcp`) — https://policylayer.com/tools/108yen-task-orchestrator-mcp.md
- Homepage: https://github.com/108yen/task-orchestrator-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "deleteTask",
    "arguments": {}
  }
}
```

## Why deleteTask is rated Critical

This tool permanently removes task data with no apparent undo mechanism. Deletion is irreversible and falls under the Destructive category, which is more severe than Write (which covers reversible modifications). The high severity reflects that an AI agent could inadvertently destroy important task records, affecting workflow orchestration and data integrity. Confidence is high because the intent is unambiguous.

From the tool's own definition: "Tool name is 'deleteTask' and description states 'Delete a task by its ID'. The verb 'Delete' indicates irreversible removal of data."

## Use case

AI agents call deleteTask to permanently remove resources in Task Orchestrator, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Task Orchestrator:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteTask"
  ]
}
```

## Other tools on Task Orchestrator (6)

- `getTask` — Read — https://policylayer.com/tools/108yen-task-orchestrator-mcp/gettask.md
- `listTasks` — Read — https://policylayer.com/tools/108yen-task-orchestrator-mcp/listtasks.md
- `completeTask` — Write — https://policylayer.com/tools/108yen-task-orchestrator-mcp/completetask.md
- `createTask` — Write — https://policylayer.com/tools/108yen-task-orchestrator-mcp/createtask.md
- `startTask` — Write — https://policylayer.com/tools/108yen-task-orchestrator-mcp/starttask.md
- `updateTask` — Write — https://policylayer.com/tools/108yen-task-orchestrator-mcp/updatetask.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=108yen-task-orchestrator-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/108yen-task-orchestrator-mcp