add_to_blacklist

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

SERVERTempo SOURCEarome3/tempo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/add-to-blacklist.md

WHAT IT DOES

What add_to_blacklist does on Tempo

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.

RISK

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 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).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_to_blacklist safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_to_blacklist, this is the rule to start with:

add_to_blacklist Rate-limited

add_to_blacklist stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every add_to_blacklist call is checked against it from then on.

FAQ

Questions about add_to_blacklist

What does the add_to_blacklist tool do? +

Add an address to a TIP-403 policy blacklist (block the address). It is categorised as a Write tool in the Tempo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_blacklist? +

Register the Tempo MCP server in PolicyLayer and add a rule for add_to_blacklist: 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 Tempo. Nothing to install.

What risk level is add_to_blacklist? +

add_to_blacklist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_to_blacklist? +

Yes. Add a rate_limit block to the add_to_blacklist 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.

How do I block add_to_blacklist completely? +

Set action: deny in the PolicyLayer policy for add_to_blacklist. 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.

What MCP server provides add_to_blacklist? +

add_to_blacklist is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →