# get_rugsense_track_record

The leakage-free scoreboard of every RugSense verdict: avoid.precisionPct = share of resolved

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

## Facts

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

## Why get_rugsense_track_record is rated Low

This is a read-only query operation that retrieves historical verdict accuracy data. It neither modifies data, executes operations, deletes information, nor involves financial transactions. The low severity reflects that retrieving historical scoring accuracy poses minimal risk even if misused by an agent.

From the tool's own definition: "Tool name 'get_rugsense_track_record' and description indicate it retrieves/queries a 'scoreboard of every RugSense verdict' showing historical accuracy metrics ('avoid.precisionPct')."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

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

## 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_base_launches` — Read — https://policylayer.com/tools/0xcnr0-rugsense/get-base-launches.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