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.
This record as markdown: /tools/0x402-mcp/get-listing.md
What get_listing does on 0x402
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | Yes | ERC-20 contract address on 0G testnet. |
Parameters from the server's own tool schema.
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 signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs get_listing safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0x402, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_listing, this is the rule to start with:
get_listing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0x402, apply this rule, and every get_listing call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the 0x402 MCP Server, which means it retrieves data without modifying state.
get_listing accepts 1 parameter: token. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the 0x402 MCP server in PolicyLayer and add a rule for get_listing: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 0x402. Nothing to install.
get_listing is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_listing rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_listing. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_listing is provided by the 0x402 MCP server (@0x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0x402, and thousands of servers like it.
This server
Across the catalogue