Tools: Policy

Seashail evaluates every write tool call against policy before decrypting key material. Policy controls tiered approval (auto-approve / confirm / hard-block), per-surface operation toggles, transaction limits, and address allowlisting.

See also:

• Policy & Approvals Guide
• Write Tools — the tools that policy gates

get_policy

Returns the effective policy configuration. When wallet is provided, returns the effective policy for that wallet (global defaults merged with any wallet-specific overrides).

Response

The response is the full Policy object with all fields and their current values. When no overrides are set, all fields return their defaults:

{
  "auto_approve_usd": 10.0,
  "confirm_up_to_usd": 1000.0,
  "hard_block_over_usd": 1000.0,
  "max_usd_per_tx": 100.0,
  "max_usd_per_day": 500.0,
  "max_slippage_bps": 100,
  "deny_unknown_usd_value": true,
  "require_user_confirm_for_remote_tx": true,
  "enable_send": true,
  "enable_swap": true,
  "enable_perps": true,
  "enable_nft": true,
  "enable_pumpfun": true,
  "enable_bridge": true,
  "enable_lending": true,
  "enable_staking": true,
  "enable_liquidity": true,
  "enable_prediction": true,
  "enable_ofac_sdn": true,
  "send_allow_any": false,
  "send_allowlist": [],
  "contract_allow_any": false,
  "contract_allowlist": [],
  "max_leverage": 3,
  "max_usd_per_position": 100.0,
  "max_usd_per_nft_tx": 100.0,
  "pumpfun_max_sol_per_buy": 0.1,
  "pumpfun_max_buys_per_hour": 10,
  "max_usd_per_bridge_tx": 100.0,
  "max_usd_per_lending_tx": 200.0,
  "max_usd_per_stake_tx": 500.0,
  "max_usd_per_liquidity_tx": 100.0,
  "max_usd_per_prediction_tx": 100.0
}

Examples

Get the global default policy:

{}

Get the effective policy for a specific wallet (includes wallet overrides when present):

{ "wallet": "my-wallet" }

update_policy

Updates policy rules. Only the fields you include are changed — all other fields keep their current values.

Response

Returns the full updated policy object (same shape as get_policy response).

Examples

Update global tiered approval thresholds:

{
  "policy": {
    "auto_approve_usd": 5,
    "confirm_up_to_usd": 500
  }
}

Set a wallet-specific override (lower per-transaction limit for a hot wallet):

{
  "wallet": "hot-wallet",
  "policy": {
    "max_usd_per_tx": 10
  }
}

Clear a wallet override (revert to global defaults):

{ "wallet": "hot-wallet", "clear": true }

Disable specific operation surfaces:

{
  "policy": {
    "enable_perps": false,
    "enable_pumpfun": false,
    "enable_prediction": false
  }
}

Configure address allowlisting for sends:

{
  "policy": {
    "send_allow_any": false,
    "send_allowlist": [
      "11111111111111111111111111111111",
      "0x742d35Cc6634C0532925a3b844Bc9e7595f2bD18"
    ]
  }
}

Policy Fields Reference

All policy fields, grouped by category. Defaults are sourced from the Seashail Rust source (policy.rs Default impl).

Tiered Approval

These three fields define the approval tiers for transactions based on USD value:

A transaction at $50 with defaults: $50 > auto_approve_usd (10) → confirmation required; $50 ≤ confirm_up_to_usd (1000) → allowed after user confirms.

Transaction Limits

Safety Controls

Operation Toggles

Each toggle enables or disables an entire operation surface. When disabled, any tool call for that surface is rejected before policy evaluation.

Address Allowlisting

Per-Surface Limits

Per-surface caps are enforced in addition to the global max_usd_per_tx and tiered approval thresholds.

How Policy Evaluation Works

Every write tool call goes through this evaluation flow before key material is decrypted:

1. Operation toggle — Is the surface enabled? (enable_send, enable_swap, etc.) If disabled → blocked.
2. Per-surface limit — Does the transaction exceed the surface-specific cap? (max_usd_per_nft_tx, max_leverage, pumpfun_max_sol_per_buy, etc.) If exceeded → blocked.
3. Address allowlist — Is the recipient/contract on the allowlist? (send_allowlist, contract_allowlist). If not → blocked.
4. Per-transaction limit — Does the amount exceed max_usd_per_tx? If exceeded → blocked.
5. Tiered approval — Where does the USD amount fall?
   • Below auto_approve_usd → auto-approved
   • Between auto_approve_usd and confirm_up_to_usd → user confirmation required (MCP elicitation)
   • Above hard_block_over_usd → hard-blocked
6. Unknown USD value — If deny_unknown_usd_value is true and pricing is unavailable → blocked (fail closed).
7. Remote transaction — If require_user_confirm_for_remote_tx is true and the transaction bytes were constructed remotely → user confirmation required.
8. Daily aggregate — Would this transaction push the day's total above max_usd_per_day? If so → blocked.

Notes:

• Prefer: get_policy first, then modify only the intended fields, then update_policy. This reduces the chance of accidentally loosening unrelated safeguards.
• Wallet-specific overrides replace the global defaults entirely (they do not merge field-by-field). When in doubt, get_policy with the wallet name to see the effective configuration.

See also:

• Policy & Approvals Guide
• Write Tools — send, swap, bridge, lend, and other policy-gated tools