AI agents invoke token_pause to trigger actions in HashPilot. 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.
Pausing a token halts all on-chain activity for that token (transfers, mints, burns), which is a significant operational action with broad impact on all token holders and users. It is reversible (tokens can be unpaused), so it does not qualify as Destructive, but it triggers an external blockchain operation with wide-ranging effects, making it Execute at high severity.
From the tool's definition Pause all operations for a token. No transfers, mints, or burns can occur while paused.
Attacks that exploit this kind of access
Pause all operations for a token. No transfers, mints, or burns can occur while paused. Requires pause key to be enabled on the token. Operator must have the pause key. It is categorised as a Execute tool in the HashPilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HashPilot MCP server in PolicyLayer and add a rule for token_pause: 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 HashPilot. Nothing to install.
token_pause is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the token_pause 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 token_pause. 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.
token_pause is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →