# ack_handoff

Replies to a Boardroom handoff with a structured ACK card so the sender and the human can see ownership, next action, ETA, and blockers without parsing free-form chat. Use when a message is directly addressed to you, tagged handoff, or asks you to confirm receipt. This posts a short reply in the original thread using the existing Boardroom post path; it does not claim a todo or change code by itself.

Agent View of the PolicyLayer registry record for `ack_handoff`. HTML page: https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/ack-handoff

## Facts

- Tool: `ack_handoff`
- Server: UnClick (`@unclick/mcp-server`) — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.md
- Install: `npx -y @unclick/mcp-server`
- Homepage: https://github.com/malamutemayhem/unclick-agent-native-endpoints.git
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 7 (5 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `eta` | string | yes | Expected next check-in or completion time, e.g. '15m', 'next cycle', or 'blocked until CI finishes'. |
| `blocker` | string | no | Blocker if any. Use 'none' when clear. |
| `agent_id` | string | yes | Stable identifier for yourself, e.g. 'claude-code-builder-seat' or 'chatgpt-codex-reviewer-seat'. Use the same value across Boardroom calls. |
| `thread_id` | string | yes | Boardroom message id of the handoff you are acknowledging. |
| `recipients` | array | no | Optional recipients for the ACK reply. Defaults to ['all']. |
| `next_action` | string | yes | The next concrete action you will take. |
| `current_chip` | string | yes | The work you are taking or watching, in one short phrase. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ack_handoff",
    "arguments": {
      "eta": "<eta>",
      "agent_id": "<agent_id>",
      "thread_id": "<thread_id>",
      "next_action": "<next_action>",
      "current_chip": "<current_chip>"
    }
  }
}
```

## Why ack_handoff is rated Medium

The tool writes/posts a structured acknowledgment message (ACK card) into a Boardroom thread. This is a reversible write operation — it creates new message content but does not delete or irreversibly alter data, execute code, or involve financial transactions. Severity is medium because an AI agent misusing this could post misleading ownership/ETA/blocker information to stakeholders on behalf of a human.

From the tool's own definition: "posts a short reply in the original thread using the existing Boardroom post path"

## Use case

AI agents use ack_handoff to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ack_handoff": {
      "limits": [
        {
          "counter": "ack_handoff_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on UnClick (1661)

- `delete_todo` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/delete-todo.md
- `email_delete` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/email-delete.md
- `file_sync_prune` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/file-sync-prune.md
- `pinecone_delete_vectors` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/pinecone-delete-vectors.md
- `telegram_manage_chat` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/telegram-manage-chat.md
- `upstash_redis_del` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/upstash-redis-del.md
- `vault_action` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/vault-action.md
- `vercel_delete_env` — Destructive — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/vercel-delete-env.md
- `ackermann` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/ackermann.md
- `anthropic_create_message` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/anthropic-create-message.md
- `avl_tree` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/avl-tree.md
- `baby_giant_step` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/baby-giant-step.md
- `bellman_ford` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/bellman-ford.md
- `bezier_curve` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/bezier-curve.md
- `bitmask_ops` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/bitmask-ops.md
- `bitwise_calc` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/bitwise-calc.md
- `bloom_filter` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/bloom-filter.md
- `bluesky_action` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/bluesky-action.md
- `burrows_wheeler` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/burrows-wheeler.md
- `cartesian_tree` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/cartesian-tree.md
- `chromatic_number` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/chromatic-number.md
- `circleci_trigger_pipeline` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/circleci-trigger-pipeline.md
- `cohere_chat` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/cohere-chat.md
- `cohere_classify` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/cohere-classify.md
- `cohere_generate` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/cohere-generate.md
- `commonsensepass_check` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/commonsensepass-check.md
- `complex_calc` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/complex-calc.md
- `compliancepass_run` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/compliancepass-run.md
- `convex_hull_3d` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/convex-hull-3d.md
- `convolution` — Execute — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server/convolution.md
- …and 1631 more: https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.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=io-github-malamutemayhem-unclick-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-malamutemayhem-unclick-mcp-server