AI agents call bridge_token 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 queries information about a token on a specific blockchain without modifying, executing, or transacting anything. It is a straightforward data retrieval operation, placing it in the Read category with low severity since misuse would only expose information, not affect assets or operations.
From the tool's definition Tool name 'bridge_token' combined with description 'Get info for a specific token on a chain' indicates a retrieval operation. The verb 'Get' and noun 'info' are unambiguously read-only operations with no side effects.
Attacks that exploit this kind of access
Get info for a specific token on a chain. 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_token: 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_token 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_token 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_token. 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_token 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 →