enable_trading
Enable trading for a tax token contract with specified parameters
This record as markdown: /tools/chulanpro5-evm-mcp-server/enable-trading.md
What enable_trading does on EVM MCP Server
AI agents invoke enable_trading to trigger actions in EVM 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 enable_trading is rated High
This tool executes a smart contract function call that enables trading on a tax token contract. While it modifies on-chain state (a Write-level concern), the action triggers an external blockchain transaction with potentially irreversible consequences (trading once enabled typically cannot be disabled), and the effects depend on the contract's implementation.
From the tool's definition "Enable trading for a tax token contract with specified parameters" — triggers an on-chain state change on a deployed smart contract that activates trading functionality
Attacks that exploit this kind of access
The rule that runs enable_trading safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_trading, this is the rule to start with:
enable_trading 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.
The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every enable_trading call is checked against it from then on.
Questions about enable_trading
Enable trading for a tax token contract with specified parameters. It is categorised as a Execute tool in the EVM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for enable_trading: 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 EVM MCP Server. Nothing to install.
enable_trading 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 enable_trading 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 enable_trading. 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.
enable_trading is provided by the EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EVM MCP Server, and thousands of servers like it.
Across the catalogue