# add_to_blacklist

Add an address to a TIP-403 policy blacklist (block the address).

Agent View of the PolicyLayer registry record for `add_to_blacklist`. HTML page: https://policylayer.com/tools/arome3-tempo-mcp/add-to-blacklist

## Facts

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

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

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

## Why add_to_blacklist is rated Medium

This tool modifies blockchain state by adding an address to a blacklist, preventing that address from transacting. While it has significant business impact (blocking user access), it is reversible—addresses can be removed from the blacklist. It does not permanently delete data or irreversibly destroy assets, so it does not qualify as Destructive.

From the tool's own definition: "Tool description states 'Add an address to a TIP-403 policy blacklist (block the address)' — this creates or modifies a blacklist data structure by adding an entry, which is a reversible write operation (the address can be removed later)."

## Use case

AI agents use add_to_blacklist to create or update resources in Tempo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tempo environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_to_blacklist": {
      "limits": [
        {
          "counter": "add_to_blacklist_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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
- `batch_payments` — Financial — https://policylayer.com/tools/arome3-tempo-mcp/batch-payments.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
- …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