# transfer_work_item_between_boards

Transfer one existing card identity to a column on another operating board. This is NOT a copy and NOT a workflow promotion: the server keeps the work-item id and every item-linked comment, criterion, task, QA-evidence row, release link and SCM link; closes the old board dwell; and opens the destination dwell in one transaction. Use move_work_item for a column on the same board. A transfer needs BOTH destination ids so a column from a different board cannot be attached accidentally.${GOVERNED_NOTE}

Agent View of the PolicyLayer registry record for `transfer_work_item_between_boards`. HTML page: https://policylayer.com/tools/adrata-adrata-mcp/transfer-work-item-between-boards

## Facts

- Tool: `transfer_work_item_between_boards`
- Server: Adrata (`@adrata/adrata-mcp`) — https://policylayer.com/tools/adrata-adrata-mcp.md
- Install: `npx -y @adrata/adrata-mcp`
- Homepage: https://www.npmjs.com/package/@adrata/adrata-mcp
- Risk category: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

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

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

## Why transfer_work_item_between_boards is rated Critical

transfer_work_item_between_boards moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents use transfer_work_item_between_boards to commit financial operations through Adrata, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adrata:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_work_item_between_boards": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Adrata (394)

- `bulk_delete_buyer_groups` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/bulk-delete-buyer-groups.md
- `cancel_agent_task` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/cancel-agent-task.md
- `delete_action` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-action.md
- `delete_buyer_group` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-buyer-group.md
- `delete_company` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-company.md
- `delete_note` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-note.md
- `delete_opportunity` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-opportunity.md
- `delete_partner` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-partner.md
- `delete_person` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-person.md
- `delete_webhook` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-webhook.md
- `delete_work_item` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-work-item.md
- `delete_work_item_acceptance_criterion` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-work-item-acceptance-criterion.md
- `flag_work_item` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/flag-work-item.md
- `forget` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/forget.md
- `paper_delete_document` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/paper-delete-document.md
- `paper_revoke_share` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/paper-revoke-share.md
- `remove_buyer_group_member` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/remove-buyer-group-member.md
- `remove_work_item_from_launch` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/remove-work-item-from-launch.md
- `requeue_work_item_qa_after_fix` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/requeue-work-item-qa-after-fix.md
- `tag_work_item_criterion_staging_only` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/tag-work-item-criterion-staging-only.md
- `unblock_work_item` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/unblock-work-item.md
- `unfile_document` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/unfile-document.md
- `unlink_proposition` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/unlink-proposition.md
- `unrelate_decisions` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/unrelate-decisions.md
- `adrata_ai_tool_execute` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/adrata-ai-tool-execute.md
- `adrata_api_request` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/adrata-api-request.md
- `attribute_partner_to_deal` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/attribute-partner-to-deal.md
- `block_work_item` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/block-work-item.md
- `build_pursuit_command_center` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/build-pursuit-command-center.md
- `draft_workflow` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/draft-workflow.md
- …and 364 more: https://policylayer.com/tools/adrata-adrata-mcp.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=adrata-adrata-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adrata-adrata-mcp