# check_address_type

A read tool on the Token Info MCP Server MCP server.

Agent View of the PolicyLayer registry record for `check_address_type`. HTML page: https://policylayer.com/tools/0xwuchuan-token-info-mcp/check-address-type

## Facts

- Tool: `check_address_type`
- Server: Token Info MCP Server (`0xwuchuan/token-info-mcp`) — https://policylayer.com/tools/0xwuchuan-token-info-mcp.md
- Homepage: https://github.com/0xwuchuan/token-info-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_address_type",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Token Info MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_address_type": {}
  }
}
```

## Other tools on Token Info MCP Server (2)

- `get_contract_roles` — Read — https://policylayer.com/tools/0xwuchuan-token-info-mcp/get-contract-roles.md
- `get_proxy_admin` — Read — https://policylayer.com/tools/0xwuchuan-token-info-mcp/get-proxy-admin.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xwuchuan-token-info-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xwuchuan-token-info-mcp