check_address_type
A read tool on the Token Info MCP server.
This record as markdown: /tools/0xwuchuan-token-info-mcp/check-address-type.md
What check_address_type does on Token Info MCP Server
AI agents call check_address_type to retrieve information from Token Info 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 check_address_type is rated Low
This tool appears to classify or identify an Ethereum address type (contract vs EOA, proxy vs implementation, etc.) without modifying state. It fits the Read category as a lookup/detection function. Confidence is moderate (0.85) due to empty description; if the tool actually executes arbitrary operations, severity could increase, but context strongly suggests passive inspection.
From the tool's definition Tool name 'check_address_type' suggests a query/inspection function. Server context indicates 'smart contract analysis' and 'detection' of contract types. Sibling tools 'get_contract_roles' and 'get_proxy_admin' are clearly read operations.
Attacks that exploit this kind of access
The rule that runs check_address_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Token Info MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_address_type, this is the rule to start with:
check_address_type 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 Token Info MCP Server, apply this rule, and every check_address_type call is checked against it from then on.
Questions about check_address_type
check_address_type is a read tool on the Token Info MCP Server MCP server. It is categorised as a Read tool in the Token Info MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Token Info MCP Server MCP server in PolicyLayer and add a rule for check_address_type: 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 Token Info MCP Server. Nothing to install.
check_address_type 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 check_address_type 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 check_address_type. 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.
check_address_type is provided by the Token Info MCP Server MCP server (0xwuchuan/token-info-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Token Info MCP Server, and thousands of servers like it.
This server
Across the catalogue