singularityagent__inspect_payment

Before signing a payment somebody else asked you to make, find out whether it can be paid at all. Takes an invoice or payment intent in the shape it arrived — payee, token, claimed ticker, amount, base units, decimals, expiry — and checks each claim against the chain instead of against the rest of the invoice. Works on Solana and on EVM chains, reading each family's own failure modes. Everywhere: a token address that is well-formed with no token at it, a displayed amount and a base-unit amount that disagree, decimals that do not match the token, a ticker naming one token while the address names another, and an expiry already passed. On Solana it also reads the destination token account — whether it exists, holds that mint, is frozen, or belongs to somebody other than the payee named — and whether the mint charges a transfer fee, which makes the payee receive less than you send. On EVM it reads whether the payee is the zero address, the token's own contract (one of the most common ways ERC-20s are permanently lost), or a contract that may be unable to move the token out again. Reach for it whenever a payment demand arrives from anywhere you do not control — an exchange, an API, a marketplace, another agent — and before building or signing anything against it. verdict is unpayable when at least one finding means signing cannot do what the demand says, payable when every stated claim checked out, and unproven when the chain could not be read, which is not the same as cleared. Read findings before verdict. This reads: it builds nothing, signs nothing and sends nothing, and unpayable means the demand is wrong rather than that the counterparty is dishonest — a typo in somebody else's configuration produces exactly this. It is categorised as a Financial tool in the Rokha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

singularityagent__inspect_payment accepts 12 parameters: to, memo, mint, asset, chain, token, amount, decimals, expiresAt, reference, tokenAccount, amountBaseUnits. The full parameter table on this page comes from the server's own tool schema.

Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__inspect_payment: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rokha. Nothing to install.

singularityagent__inspect_payment is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Yes. Add a rate_limit block to the singularityagent__inspect_payment rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

Set action: deny in the PolicyLayer policy for singularityagent__inspect_payment. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

singularityagent__inspect_payment is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.