High Risk →

unpause_token

Resume transfers on a paused TIP-20 token. Requires UNPAUSE_ROLE.

How to control unpause_token ↓

What unpause_token does on Tempo

AI agents invoke unpause_token to trigger actions in Tempo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why unpause_token needs a policy

Unpausing a token resumes all token transfers on the blockchain, which is an irreversible state change that triggers external operations with broad financial impact. It's not purely destructive (it enables activity rather than deleting data), but it executes a privileged blockchain state change that re-enables financial flows across all token holders.

From the tool's definition Resume transfers on a paused TIP-20 token. Requires UNPAUSE_ROLE.

Documented attack patterns abuse exactly the kind of access unpause_token gives an agent:

How to control unpause_token

PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for unpause_token:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "unpause_token": {
      "limits": [
        {
          "counter": "unpause_token_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

unpause_token stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tempo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about unpause_token

What does the unpause_token tool do? +

Resume transfers on a paused TIP-20 token. Requires UNPAUSE_ROLE. It is categorised as a Execute tool in the Tempo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on unpause_token? +

Register the Tempo MCP server in PolicyLayer and add a rule for unpause_token: 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 unpause_token? +

unpause_token is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit unpause_token? +

Yes. Add a rate_limit block to the unpause_token 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 unpause_token completely? +

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

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

Enforce policy on every Tempo tool call.

Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.