# listTasks

List tasks from hierarchical structure, optionally filtered by parentId. Returns root tasks if no parentId specified, or direct children of specified parent task.

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

## Facts

- Tool: `listTasks`
- 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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why listTasks is rated Low

This tool queries and retrieves task data from a hierarchy without creating, modifying, deleting, or executing any operations. It is purely informational, matching the Read category definition. The blast radius is minimal as it only exposes existing task structure data.

From the tool's own definition: "Tool name 'listTasks' and description 'List tasks from hierarchical structure, optionally filtered by parentId."

Risk signals: Admin/system-level operation

## Use case

AI agents call listTasks to retrieve information from Task Orchestrator without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "listTasks": {}
  }
}
```

## Other tools on Task Orchestrator (6)

- `deleteTask` — Destructive — https://policylayer.com/tools/108yen-task-orchestrator-mcp/deletetask.md
- `getTask` — Read — https://policylayer.com/tools/108yen-task-orchestrator-mcp/gettask.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