pause_token
Emergency pause all transfers on a TIP-20 token. Requires PAUSE_ROLE.
This record as markdown: /tools/arome3-tempo-mcp/pause-token.md
What pause_token does on Tempo
AI agents use pause_token to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pause_token is rated Critical
Pausing all transfers on a payment token halts all financial activity for that token across all users. This is a high-impact financial operation that can freeze funds and prevent any transactions from occurring, representing a critical blast radius. It is irreversible in effect until unpaused, and operates on a financial instrument (stablecoin payments).
From the tool's definition Emergency pause all transfers on a TIP-20 token
Attacks that exploit this kind of access
The rule that runs pause_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 pause_token, this is the rule to start with:
Any call to pause_token is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every pause_token call is checked against it from then on.
Questions about pause_token
Emergency pause all transfers on a TIP-20 token. Requires PAUSE_ROLE. It is categorised as a Financial tool in the Tempo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tempo MCP server in PolicyLayer and add a rule for pause_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.
pause_token is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pause_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.
Set action: deny in the PolicyLayer policy for pause_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.
pause_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.
More on Tempo, and thousands of servers like it.
Across the catalogue