Get metadata for an ERC-20 token contract: name, symbol, decimals,
AI agents call token_info to retrieve information from Kxcoscan AI Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns read-only metadata about ERC-20 token contracts. It retrieves information (name, symbol, decimals) without creating, modifying, or destroying any data, and does not execute code or trigger external operations. The low severity reflects minimal blast radius—even if misused by an AI agent, the tool can only return public blockchain data without side effects.
From the tool's definition Tool name 'token_info' and description 'Get metadata for an ERC-20 token contract: name, symbol, decimals' indicate pure data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get metadata for an ERC-20 token contract: name, symbol, decimals,. It is categorised as a Read tool in the Kxcoscan AI Tools MCP Server, which means it retrieves data without modifying state.
Register the Kxcoscan AI Tools MCP server in PolicyLayer and add a rule for 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 Kxcoscan AI Tools. Nothing to install.
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 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 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.
token_info is provided by the Kxcoscan AI Tools MCP server (keralpatel/kxcoscan-mcp-server). 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 →