spraay_bridge_chains

List all chains supported by the Spraay bridge aggregator (LI.FI). Returns chain names, IDs, and supported tokens. Costs $0.001 USDC.

SERVERSpraay X402 Mcp SOURCEspraay-x402-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-plagtech-spraay-x402-mcp/spraay-bridge-chains.md

WHAT IT DOES

What spraay_bridge_chains does on Spraay X402 Mcp

AI agents call spraay_bridge_chains to retrieve information from Spraay X402 Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why spraay_bridge_chains is rated Low

This tool queries and returns reference data about supported chains and tokens. While it incurs a small cost ($0.001 USDC), the cost is nominal and fixed, and there is no financial transaction initiated by the tool itself — it is a simple informational lookup. The blast radius is minimal: querying supported chains cannot cause harm or loss. Classified as Read with low severity.

From the tool's definition Tool description states 'List all chains supported by the Spraay bridge aggregator' — a retrieval operation that returns data (chain names, IDs, tokens) with no modification or execution side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spraay_bridge_chains safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spraay X402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spraay_bridge_chains, this is the rule to start with:

spraay_bridge_chains Allowed

spraay_bridge_chains is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spraay_bridge_chains": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spraay X402 Mcp, apply this rule, and every spraay_bridge_chains call is checked against it from then on.

FAQ

Questions about spraay_bridge_chains

What does the spraay_bridge_chains tool do? +

List all chains supported by the Spraay bridge aggregator (LI.FI). Returns chain names, IDs, and supported tokens. Costs $0.001 USDC. It is categorised as a Read tool in the Spraay X402 Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spraay_bridge_chains? +

Register the Spraay X402 MCP server in PolicyLayer and add a rule for spraay_bridge_chains: 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 Spraay X402 Mcp. Nothing to install.

What risk level is spraay_bridge_chains? +

spraay_bridge_chains is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit spraay_bridge_chains? +

Yes. Add a rate_limit block to the spraay_bridge_chains 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.

How do I block spraay_bridge_chains completely? +

Set action: deny in the PolicyLayer policy for spraay_bridge_chains. 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.

What MCP server provides spraay_bridge_chains? +

spraay_bridge_chains is provided by the Spraay X402 MCP server (spraay-x402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spraay X402, and thousands of servers like it.

This server

All 183 Spraay X402 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →