# batch_payments

Send multiple TIP-20 stablecoin payments in a single atomic transaction.

Agent View of the PolicyLayer registry record for `batch_payments`. HTML page: https://policylayer.com/tools/arome3-tempo-mcp/batch-payments

## Facts

- Tool: `batch_payments`
- Server: Tempo (`arome3/tempo-mcp`) — https://policylayer.com/tools/arome3-tempo-mcp.md
- Homepage: https://github.com/arome3/tempo-mcp
- Risk category: Financial (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "batch_payments",
    "arguments": {}
  }
}
```

## Why batch_payments is rated Critical

This tool executes real financial transactions by sending stablecoin payments on the Tempo blockchain. The batch/atomic nature amplifies the blast radius: a single misuse could drain funds to multiple addresses simultaneously with no reversal. This clearly falls under Financial, the most severe category, with critical severity due to the multiplied impact of batch execution.

From the tool's own definition: "'Send multiple TIP-20 stablecoin payments in a single atomic transaction' — directly moves stablecoin funds to multiple recipients in one operation"

## Use case

AI agents use batch_payments to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tempo:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_payments": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Tempo (60)

- `burn_blocked_tokens` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/burn-blocked-tokens.md
- `burn_tokens` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/burn-tokens.md
- `remove_fee_liquidity` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/remove-fee-liquidity.md
- `remove_from_whitelist` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/remove-from-whitelist.md
- `renounce_role` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/renounce-role.md
- `revoke_access_key` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/revoke-access-key.md
- `revoke_role` — Destructive — https://policylayer.com/tools/arome3-tempo-mcp/revoke-role.md
- `unpause_token` — Execute — https://policylayer.com/tools/arome3-tempo-mcp/unpause-token.md
- `add_fee_liquidity` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/add-fee-liquidity.md
- `cancel_order` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/cancel-order.md
- `cancel_scheduled_payment` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/cancel-scheduled-payment.md
- `claim_rewards` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/claim-rewards.md
- `create_token` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/create-token.md
- `distribute_rewards` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/distribute-rewards.md
- `mint_tokens` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/mint-tokens.md
- `opt_in_rewards` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/opt-in-rewards.md
- `opt_out_rewards` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/opt-out-rewards.md
- `pause_token` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/pause-token.md
- `place_flip_order` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/place-flip-order.md
- `place_limit_order` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/place-limit-order.md
- `schedule_payment` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/schedule-payment.md
- `send_concurrent_payments` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/send-concurrent-payments.md
- `send_payment` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/send-payment.md
- `send_sponsored_payment` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/send-sponsored-payment.md
- `swap_stablecoins` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/swap-stablecoins.md
- `check_transfer_compliance` — Read — https://policylayer.com/tools/arome3-tempo-mcp/check-transfer-compliance.md
- `estimate_fee_swap` — Read — https://policylayer.com/tools/arome3-tempo-mcp/estimate-fee-swap.md
- `estimate_sponsored_gas` — Read — https://policylayer.com/tools/arome3-tempo-mcp/estimate-sponsored-gas.md
- `get_access_key_info` — Read — https://policylayer.com/tools/arome3-tempo-mcp/get-access-key-info.md
- `get_account_info` — Read — https://policylayer.com/tools/arome3-tempo-mcp/get-account-info.md
- …and 30 more: https://policylayer.com/tools/arome3-tempo-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=arome3-tempo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/arome3-tempo-mcp