Start surge tax on your token (creator only).
AI agents invoke start_surge_tax to trigger actions in Basis MCP Server. 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.
This tool executes a blockchain transaction that activates a surge tax on a token, affecting all holders and traders of that token. While it doesn't directly move money, it modifies on-chain contract behavior in a way that can significantly impact token economics and trading conditions.
From the tool's definition 'Start surge tax on your token (creator only)' — triggers an on-chain operation that activates a surge tax mechanism on a deployed token contract
Attacks that exploit this kind of access
Start surge tax on your token (creator only). It is categorised as a Execute tool in the Basis MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for start_surge_tax: 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 Basis MCP Server. Nothing to install.
start_surge_tax 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 start_surge_tax 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 start_surge_tax. 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.
start_surge_tax is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →