# check_base_token

Deep-score ONE Base token by address — the

Agent View of the PolicyLayer registry record for `check_base_token`. HTML page: https://policylayer.com/tools/0xcnr0-rugsense/check-base-token

## Facts

- Tool: `check_base_token`
- Server: RugSense (`0xcnr0/rugsense`) — https://policylayer.com/tools/0xcnr0-rugsense.md
- Homepage: https://github.com/0xcnr0/rugsense
- 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": "check_base_token",
    "arguments": {}
  }
}
```

## Why check_base_token is rated Low

This tool retrieves and analyzes blockchain token data without modifying state, executing code, or initiating financial transactions directly. However, severity is elevated to medium because the output (risk/opportunity scores and trading recommendations) is designed to inform financial decisions by agents, creating indirect financial risk if scores are misused or if the tool is compromised.

From the tool's own definition: "Tool name 'check_base_token' and description indicate scoring/analysis of a single token by address. No modification, deletion, or execution of commands. Returns structured launch data (opportunity/risk scores, AVOID/WATCH/HOT decisions) for analysis purposes."

## Use case

AI agents call check_base_token to retrieve information from RugSense 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 RugSense:

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

## Other tools on RugSense (6)

- `check_base_tokens_batch` — Read — https://policylayer.com/tools/0xcnr0-rugsense/check-base-tokens-batch.md
- `get_base_deployer_dossier` — Read — https://policylayer.com/tools/0xcnr0-rugsense/get-base-deployer-dossier.md
- `get_base_launches` — Read — https://policylayer.com/tools/0xcnr0-rugsense/get-base-launches.md
- `get_rugsense_track_record` — Read — https://policylayer.com/tools/0xcnr0-rugsense/get-rugsense-track-record.md
- `quick_check_base_token` — Read — https://policylayer.com/tools/0xcnr0-rugsense/quick-check-base-token.md
- `watch_base_token` — Read — https://policylayer.com/tools/0xcnr0-rugsense/watch-base-token.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=0xcnr0-rugsense · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xcnr0-rugsense