insidercable.com

The 'paid' parameter instructs the agent to retry failed calls by attaching a signed payment object (_meta["x402/payment"] or PAYMENT-SIGNATURE header) in order to unlock a 'live tier'. This pattern, repeated identically across all seven tools, could lead an agent to autonomously construct and attach a cryptographic payment credential/signature and execute a real monetary transaction in response to a PaymentRequired error, without the user having explicitly reviewed or approved that specific charge. Agents should not be instructed via tool descriptions to automatically retry with signed payment attached; this should require explicit per-transaction user confirmation.

Same x402 auto-retry-with-payment pattern as in congress_trades: the description tells the agent exactly how to attach a signed payment to bypass the PaymentRequired response, risking unapproved spend if the agent follows this literally without checking with the user first.

Same x402 auto-retry-with-payment pattern as in congress_trades, present in this tool's 'paid' field description.

Same x402 auto-retry-with-payment pattern as in congress_trades, present in this tool's 'paid' field description.

Same x402 auto-retry-with-payment pattern as in congress_trades, present in this tool's 'paid' field description. Additionally this tool deals with on-chain token launch data where 'ticker' is explicitly noted as 'untrusted text' — a good practice, but combined with the payment-retry instruction increases risk if the agent chains automated payment with unverified on-chain identifiers.

Same x402 auto-retry-with-payment pattern as in congress_trades, present in this tool's 'paid' field description.

Same x402 auto-retry-with-payment pattern as in congress_trades, present in this tool's 'paid' field description.