Seashail

Policy And Approvals

Set spending caps, allowlists, and when user confirmation is required.

Seashail evaluates every write (for example send_transaction, swap_tokens) against policy before any key material is decrypted.

Tiered Approvals

The default policy is designed to:

  • auto-approve small transactions
  • require explicit user confirmation for larger ones (MCP elicitation)
  • hard-block transactions above a maximum

Common Controls

  • Per-transaction and daily USD caps: max_usd_per_tx, max_usd_per_day
  • Swap slippage cap (basis points): max_slippage_bps
  • Send allowlisting: send_allow_any, send_allowlist
  • Contract allowlisting: contract_allow_any, contract_allowlist
  • Operation toggles: enable_send, enable_swap

Viewing And Updating Policy

Use:

  • get_policy to view current policy
  • update_policy to replace policy rules

If you update policy via an agent, prefer a workflow like:

  1. Read get_policy
  2. Modify only the intended fields
  3. Apply with update_policy

This avoids accidentally loosening unrelated safeguards.

Wallets And Key Storage

Generated vs imported wallets, passphrases, and recovery shares.

Security Model

Threat model, policy enforcement, encrypted keys, and concurrency guarantees.

On this page

Tiered ApprovalsCommon ControlsViewing And Updating Policy