List all bridges available in this polybridge-mcp instance with their connection status.
AI agents call polybridge_list_bridges to retrieve information from Polybridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about available bridges and their status without creating, modifying, deleting, or executing anything. It is a straightforward read operation that provides visibility into the system's bridge configuration, analogous to a 'get' or 'list' API call.
From the tool's definition Tool name includes 'list' and description states 'List all bridges available' with 'connection status' - a pure query operation with no side effects.
Attacks that exploit this kind of access
List all bridges available in this polybridge-mcp instance with their connection status. It is categorised as a Read tool in the Polybridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Polybridge MCP server in PolicyLayer and add a rule for polybridge_list_bridges: 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 Polybridge MCP. Nothing to install.
polybridge_list_bridges 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 polybridge_list_bridges 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 polybridge_list_bridges. 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.
polybridge_list_bridges is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). 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 →