unpause_token

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

SERVERTempo SOURCEarome3/tempo-mcp

High RISK CLASS

Category Execute

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/unpause-token.md

WHAT IT DOES

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.

RISK

Why unpause_token is rated High

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unpause_token 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 unpause_token, this is the rule to start with:

unpause_token Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

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.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →