# xlayer_leaderboard

Get the ScoutAgent leaderboard on X Layer, ranked by PnL. Filter by time period.

Agent View of the PolicyLayer registry record for `xlayer_leaderboard`. HTML page: https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-leaderboard

## Facts

- Tool: `xlayer_leaderboard`
- Server: ScoutAgent (`0xcaptain888/scout-agent`) — https://policylayer.com/tools/0xcaptain888-scout-agent.md
- Homepage: https://github.com/0xCaptain888/scout-agent
- 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": "xlayer_leaderboard",
    "arguments": {}
  }
}
```

## Why xlayer_leaderboard is rated Low

This tool retrieves and displays leaderboard rankings filtered by time period. It has no side effects, does not modify data, does not execute code, does not delete anything, and does not involve financial transactions. It is purely a data retrieval operation with minimal blast radius if misused by an AI agent.

From the tool's own definition: "Tool name and description indicate retrieval of leaderboard data: 'Get the ScoutAgent leaderboard on X Layer, ranked by PnL."

## Use case

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

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

## Other tools on ScoutAgent (6)

- `xlayer_place_bet` — Financial — https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-place-bet.md
- `xlayer_get_agent_stats` — Read — https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-get-agent-stats.md
- `xlayer_get_market` — Read — https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-get-market.md
- `xlayer_list_markets` — Read — https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-list-markets.md
- `xlayer_mint_agent` — Read — https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-mint-agent.md
- `xlayer_natural_intent` — Read — https://policylayer.com/tools/0xcaptain888-scout-agent/xlayer-natural-intent.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=0xcaptain888-scout-agent · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xcaptain888-scout-agent