AI agents call bridge_tokens 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 or lists data (tokens) from specified chains with no side effects, mutations, code execution, or destructive operations. It is a straightforward read/query operation fitting the 'Read' category with low severity since it cannot be misused to cause harm—it only fetches informational data.
From the tool's definition Tool name 'bridge_tokens' and description 'Get tokens available on specified chains' indicates a query operation that retrieves information about available tokens without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get tokens available on specified chains. 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_tokens: 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_tokens 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_tokens 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_tokens. 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_tokens 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 →