# get_intelligence_token_by_chain_address

GET /intelligence/token/{chain}/{address}

Agent View of the PolicyLayer registry record for `get_intelligence_token_by_chain_address`. HTML page: https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-intelligence-token-by-chain-address

## Facts

- Tool: `get_intelligence_token_by_chain_address`
- Server: REI Crypto MCP Server (`0xreisearch/crypto-mcp-beta`) — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta.md
- Homepage: https://github.com/0xReisearch/crypto-mcp-beta
- Risk category: Read (Low risk)
- Registry record: grade B, 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": "get_intelligence_token_by_chain_address",
    "arguments": {}
  }
}
```

## Why get_intelligence_token_by_chain_address is rated Low

This is a data retrieval operation that queries crypto token intelligence for a specific blockchain address. It has no side effects, cannot modify data, and poses minimal risk if misused by an AI agent—worst case would be excessive API calls or information gathering. Categorized as Read with low severity.

From the tool's own definition: "Tool name includes 'get_' prefix and description shows GET HTTP method. Retrieves token intelligence data by chain and address parameters. No create, modify, delete, or financial operations indicated."

## Use case

AI agents call get_intelligence_token_by_chain_address to retrieve information from REI Crypto 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 REI Crypto MCP Server:

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

## Other tools on REI Crypto MCP Server (116)

- `date_to_timestamp` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/date-to-timestamp.md
- `get_active_users` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-active-users.md
- `get_api_important_entities` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-api-important-entities.md
- `get_balances_address` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-balances-address.md
- `get_balances_entity` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-balances-entity.md
- `get_batch_historical_prices` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-batch-historical-prices.md
- `get_bridge_day_stats` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-bridge-day-stats.md
- `get_bridge_details` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-bridge-details.md
- `get_bridge_transactions` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-bridge-transactions.md
- `get_bridge_volume` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-bridge-volume.md
- `get_bridges` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-bridges.md
- `get_categories` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-categories.md
- `get_chain_assets` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-chain-assets.md
- `get_chains` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-chains.md
- `get_closest_block` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-closest-block.md
- `get_coin_by_contract` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-coin-by-contract.md
- `get_coin_by_id` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-coin-by-id.md
- `get_coin_markets` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-coin-markets.md
- `get_coin_ohlc_range` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-coin-ohlc-range.md
- `get_counterparties_address` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-counterparties-address.md
- `get_counterparties_entity` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-counterparties-entity.md
- `get_current_prices` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-current-prices.md
- `get_current_time` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-current-time.md
- `get_derivatives_overview` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-derivatives-overview.md
- `get_derivatives_summary` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-derivatives-summary.md
- `get_dex_overview` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-dex-overview.md
- `get_dex_overview_by_chain` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-dex-overview-by-chain.md
- `get_dex_summary` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-dex-summary.md
- `get_emission_data` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-emission-data.md
- `get_emissions` — Read — https://policylayer.com/tools/0xreisearch-crypto-mcp-beta/get-emissions.md
- …and 86 more: https://policylayer.com/tools/0xreisearch-crypto-mcp-beta.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=0xreisearch-crypto-mcp-beta · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xreisearch-crypto-mcp-beta
