# bridge_getChainInfo

Get information about all supported chains for the 0xAINet cross-chain bridge. Returns chain IDs, names, bridge contract addresses, and RPC URLs.

Agent View of the PolicyLayer registry record for `bridge_getChainInfo`. HTML page: https://policylayer.com/tools/0xaibridge-mcp/bridge-getchaininfo

## Facts

- Tool: `bridge_getChainInfo`
- Server: 0xaibridge (`@0xaibridge/mcp`) — https://policylayer.com/tools/0xaibridge-mcp.md
- Install: `npx -y @0xaibridge/mcp`
- Homepage: https://www.npmjs.com/package/@0xaibridge/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, 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": "bridge_getChainInfo",
    "arguments": {}
  }
}
```

## Why bridge_getChainInfo is rated Low

Even though bridge_getChainInfo 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.

## Use case

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

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

## Other tools on 0xaibridge (4)

- `bridge_transfer` — Financial — https://policylayer.com/tools/0xaibridge-mcp/bridge-transfer.md
- `bridge_estimateFee` — Read — https://policylayer.com/tools/0xaibridge-mcp/bridge-estimatefee.md
- `bridge_getHealth` — Read — https://policylayer.com/tools/0xaibridge-mcp/bridge-gethealth.md
- `bridge_getRoute` — Read — https://policylayer.com/tools/0xaibridge-mcp/bridge-getroute.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=0xaibridge-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xaibridge-mcp