AI agents use eth_create_token to create or update resources in PortalMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PortalMCP environment.
This tool creates new smart contracts that represent financial tokens/assets. While it doesn't directly commit funds or move money (which would be Financial), it creates reversible digital assets that can represent value. The creation itself is a modification/write action.
From the tool's definition Tool generates a new ERC-20 token contract and is explicitly intended to be deployed afterwards via eth_deploy_contract_with_signer. Enables creation of financial assets on blockchain.
Attacks that exploit this kind of access
Generate a new ERC-20 token contract (Solidity). Deploy it afterwards with eth_compile_contract + eth_deploy_contract_with_signer. It is categorised as a Write tool in the PortalMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Portal MCP server in PolicyLayer and add a rule for eth_create_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 PortalMCP. Nothing to install.
eth_create_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the eth_create_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 eth_create_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.
eth_create_token is provided by the Portal MCP server (portalfnd/portalmcp). 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 →