Server-wallet signing fails with "signing job failed" on all chains — mm CLI setup fully verified

Hi MetaMask Agent Wallet team,

Every transfer from my server wallet fails at the signing step, on every chain I try. Balance reads, auth, and policy changes all work — only signing fails.

Error (identical every time):

Error: Policy evaluation could not be completed. Retry the request.
Hint: The signing job failed. Retry; run with --verbose for detail.

Verbose shows: WalletRuntimeError: Policy evaluation could not be completed thrown from inside the @metamask/agent-wallet package (chainId=84532, mode=server, phase=execute).

Wallet address: 0x3cc324f935ecc0c8c081bf583af811a1893877bd

Setup (all green):

mm doctor → authenticated: true, initialized: true, skill metamask-agent-wallet found and compatible: true
CLI version 6.1.3, server wallet, Guard mode

What I already verified on my side:

Sufficient balance (test ETH funded on the target chains)
Target chains are in allowed_chains (tested 84532 and 11155111)
Address allowlist and blocklist are both empty (not blocking)
Outflow limit was 0; I set rolling_24h: 100 via mm wallet policy set — this succeeded with a working email-2FA approval, so the policy service itself responds
Infura status page shows all relevant networks operational

Reproduction: The failure is identical whether I run mm transfer manually or drive it through an agent (Claude Code), and it happens on both Base Sepolia (84532) and Ethereum Sepolia (11155111) — so it is chain-independent and points to the server-side signing service, not my configuration.

Command used:

mm transfer --to 0x000000000000000000000000000000000000dEaD --amount 0.001 --token native --chain-id 84532 --wait

Could you check the signing service for my server wallet? Happy to provide request IDs or run any diagnostic you need.

Thanks,
Raphaël

Start by reproducing the command with --verbose on Base Sepolia or Ethereum Sepolia and inspect the reported WalletRuntimeError from @metamask/agent-wallet. No repository file or test is named; done would require identifying the signing-service failure and confirming that server-wallet transfers complete or documenting the required diagnostic outcome.

Written by the indexing model from the issue text.