Configure a Fireblocks Transaction Authorization Policy (TAP) rule requiring dual approval for transfers above a threshold
domain: developers.fireblocks.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve current policy via GET /v1/tx_screening/policy/snapshot to inspect active rules before modification
Construct a policy rule object with fields: type (TRANSFER), action (2-OF-N_APPROVAL), src (vault account or wildcard), dst (whitelist or wildcard), asset, amountUSDOperator (GREATER_THAN), amountUSD threshold value
POST /v1/tx_screening/policy/publish with the full updated rules array; rules are evaluated in order — place more specific rules before wildcards
Assign approvers to the rule using the Fireblocks console or POST /v1/users to confirm user roles (APPROVER, SIGNER) are set before the rule is live
Test by initiating a low-value transfer via POST /v1/transactions and verifying the transaction status moves to PENDING_AUTHORIZATION before BROADCASTING
Monitor policy changes via GET /v1/tx_screening/policy/snapshot; retain old snapshots to support audit trail requirements
Known gotchas
Publishing a new policy snapshot overwrites the entire active policy — a partial update that omits existing rules silently removes them; always fetch and merge before posting
TAP rules apply to API-initiated and console-initiated transactions equally; test in a sandbox workspace (api.sandbox.fireblocks.io) before applying to production
Approval rules that reference deleted or suspended users will cause transactions to hang in PENDING_AUTHORIZATION indefinitely with no auto-escalation by default
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?