# move-task

move a task to a different status

Agent View of the PolicyLayer registry record for `move-task`. HTML page: https://policylayer.com/tools/0thomas1-kanban-mcp/move-task

## Facts

- Tool: `move-task`
- Server: Kanban MCP Server (`0thomas1/kanban-mcp`) — https://policylayer.com/tools/0thomas1-kanban-mcp.md
- Homepage: https://github.com/0Thomas1/Kanban-MCP
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why move-task is rated Medium

This tool changes task metadata (status field) but does not delete, execute code, trigger financial transactions, or cause irreversible damage. The modification is reversible—tasks can be moved back to previous statuses. This is a classic Write operation: data modification without permanent loss.

From the tool's own definition: "Tool description states 'move a task to a different status', which modifies task state reversibly without deleting data or executing external operations."

## Use case

AI agents use move-task to create or update resources in Kanban MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kanban MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kanban MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "move-task": {
      "limits": [
        {
          "counter": "move-task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Kanban MCP Server (3)

- `add-tag` — Write — https://policylayer.com/tools/0thomas1-kanban-mcp/add-tag.md
- `create-task` — Write — https://policylayer.com/tools/0thomas1-kanban-mcp/create-task.md
- `set-prioity` — Write — https://policylayer.com/tools/0thomas1-kanban-mcp/set-prioity.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=0thomas1-kanban-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0thomas1-kanban-mcp
