transfer_work_item_between_boards

SERVERAdrata SOURCE@adrata/adrata-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/transfer-work-item-between-boards.md

WHAT IT DOES

What transfer_work_item_between_boards does on Adrata

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.

RISK

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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_work_item_between_boards safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_work_item_between_boards, this is the rule to start with:

transfer_work_item_between_boards Approval-gated

Any call to transfer_work_item_between_boards is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every transfer_work_item_between_boards call is checked against it from then on.

FAQ

Questions about transfer_work_item_between_boards

What does the transfer_work_item_between_boards tool do? +

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}. It is categorised as a Financial tool in the Adrata MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_work_item_between_boards? +

Register the Adrata MCP server in PolicyLayer and add a rule for transfer_work_item_between_boards: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Adrata. Nothing to install.

What risk level is transfer_work_item_between_boards? +

transfer_work_item_between_boards is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_work_item_between_boards? +

Yes. Add a rate_limit block to the transfer_work_item_between_boards rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block transfer_work_item_between_boards completely? +

Set action: deny in the PolicyLayer policy for transfer_work_item_between_boards. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides transfer_work_item_between_boards? +

transfer_work_item_between_boards is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge →transfer_sites on A3plus →abs_zalo_transfer_owner on Abs Zalo Bot → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →