AI agents call bridge_chains to retrieve information from Logiqical without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static configuration data about supported blockchain chains available for bridging. It performs no mutations, does not execute transactions, does not trigger external operations with side effects, and does not delete or modify data. The blast radius of misuse is minimal—an agent could only retrieve information already publicly available through the Li.Fi bridge service.
From the tool's definition Tool name 'bridge_chains' and description 'Get all supported chains' indicate a query/retrieval operation with no side effects. The verb 'Get' and the informational nature of returning a list of supported chains confirm this is a read-only operation.
Attacks that exploit this kind of access
Get all supported chains for cross-chain bridging via Li.Fi. It is categorised as a Read tool in the Logiqical MCP Server, which means it retrieves data without modifying state.
Register the Logiqical MCP server in PolicyLayer and add a rule for 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 Logiqical. Nothing to install.
bridge_chains 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 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.
Set action: deny in the PolicyLayer policy for 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.
bridge_chains is provided by the Logiqical MCP server (logiqical-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →