# get_listing

Look up a token's listing on the CollateralRegistry, fetch the seal body its sealHash points at from 0G Storage, and verify that seal locally. Answers what the chain says, what the seal says, and whether the two agree.

Agent View of the PolicyLayer registry record for `get_listing`. HTML page: https://policylayer.com/tools/0x402-mcp/get-listing

## Facts

- Tool: `get_listing`
- Server: 0x402 (`@0x402/mcp`) — https://policylayer.com/tools/0x402-mcp.md
- Install: `npx -y @0x402/mcp`
- Homepage: https://www.npmjs.com/package/@0x402/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `token` | string | yes | ERC-20 contract address on 0G testnet. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_listing",
    "arguments": {
      "token": "<token>"
    }
  }
}
```

## Why get_listing is rated Low

Even though get_listing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Handles credentials or secrets (token)

## Use case

AI agents call get_listing to retrieve information from 0x402 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 0x402:

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

## Other tools on 0x402 (6)

- `underwrite` — Execute — https://policylayer.com/tools/0x402-mcp/underwrite.md
- `agent_status` — Read — https://policylayer.com/tools/0x402-mcp/agent-status.md
- `describe_auditor` — Read — https://policylayer.com/tools/0x402-mcp/describe-auditor.md
- `hire_audit` — Read — https://policylayer.com/tools/0x402-mcp/hire-audit.md
- `quote_audit` — Read — https://policylayer.com/tools/0x402-mcp/quote-audit.md
- `verify_seal` — Read — https://policylayer.com/tools/0x402-mcp/verify-seal.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=0x402-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x402-mcp