# get_base_launches

Ranked feed of freshly-launched Base tokens, each scored for safety + momentum into one

Agent View of the PolicyLayer registry record for `get_base_launches`. HTML page: https://policylayer.com/tools/0xcnr0-rugsense/get-base-launches

## Facts

- Tool: `get_base_launches`
- 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": "get_base_launches",
    "arguments": {}
  }
}
```

## Why get_base_launches is rated Low

This tool retrieves and ranks structured data about blockchain token launches. It queries an existing database or feed, applies scoring logic server-side, and returns read-only results to the caller. The agent receives information to inform decisions but cannot modify data, execute arbitrary code, delete records, or move funds through this tool alone.

From the tool's own definition: "Tool name 'get_base_launches' and description 'Ranked feed of freshly-launched Base tokens, each scored for safety + momentum' indicate a retrieval/query operation that returns pre-computed launch data and scores."

## Use case

AI agents call get_base_launches 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": {
    "get_base_launches": {}
  }
}
```

## Other tools on RugSense (6)

- `check_base_token` — Read — https://policylayer.com/tools/0xcnr0-rugsense/check-base-token.md
- `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_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