deploy_token
Deploy a new ERC20 token contract with the specified name and symbol
This record as markdown: /tools/chulanpro5-evm-mcp-server/deploy-token.md
What deploy_token does on EVM MCP Server
AI agents invoke deploy_token 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 deploy_token is rated High
Deploying a smart contract is an Execute action—it triggers code execution on a blockchain network and creates irreversible on-chain state. While the deployment itself cannot be undone (making it destructive in nature), it is classified as Execute rather than Destructive because the primary action is executing a deployment operation, not deleting or overwriting existing data.
From the tool's definition Tool name 'deploy_token' and description 'Deploy a new ERC20 token contract' indicate execution of smart contract deployment on blockchain networks.
Attacks that exploit this kind of access
The rule that runs deploy_token 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 deploy_token, this is the rule to start with:
deploy_token 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 deploy_token call is checked against it from then on.
Questions about deploy_token
Deploy a new ERC20 token contract with the specified name and symbol. 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 deploy_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 EVM MCP Server. Nothing to install.
deploy_token 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 deploy_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 deploy_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.
deploy_token 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