New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

start_surge_tax

Start surge tax on your token (creator only).

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts
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/launch-on-basis-mcp-ts/start-surge-tax.md

What start_surge_tax does on Basis MCP Server

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.

Why start_surge_tax is rated High

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

Questions about start_surge_tax

What does the start_surge_tax tool do? +

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.

How do I enforce a policy on start_surge_tax? +

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.

What risk level is start_surge_tax? +

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

Can I rate-limit start_surge_tax? +

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.

How do I block start_surge_tax completely? +

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.

What MCP server provides start_surge_tax? +

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.

More on Basis MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Basis MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.