get_token_info
Get comprehensive information about an ERC20 token including name, symbol, decimals, total supply, and other metadata. Use this to analyze any token on EVM chains.
This record as markdown: /tools/chulanpro5-evm-mcp-server/get-token-info.md
What get_token_info does on EVM MCP Server
AI agents call get_token_info to retrieve information from EVM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_token_info is rated Low
get_token_info performs a read-only query of token metadata on EVM blockchains. It retrieves immutable data attributes without side effects, matching the 'Read' category definition (search, list, get, fetch). The low severity reflects minimal blast radius—an agent querying arbitrary token data cannot directly harm users or systems.
From the tool's definition Tool retrieves 'comprehensive information about an ERC20 token including name, symbol, decimals, total supply, and other metadata' with no indication of modifying, executing code, deleting, or moving funds.
Attacks that exploit this kind of access
The rule that runs get_token_info 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 get_token_info, this is the rule to start with:
get_token_info is read-only, so it stays allowed. 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 get_token_info call is checked against it from then on.
Questions about get_token_info
Get comprehensive information about an ERC20 token including name, symbol, decimals, total supply, and other metadata. Use this to analyze any token on EVM chains. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for get_token_info: 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.
get_token_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_token_info 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 get_token_info. 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.
get_token_info 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.
This server
Across the catalogue