Check status of cross-chain bridges
AI agents call get_bridge_status to retrieve information from JS-Peer x DeFi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the state of cross-chain bridges. While it does not modify data, the medium severity reflects that bridge status information in a DeFi context could inform high-value financial decisions or exploit detection of bridge vulnerabilities, making misuse potentially consequential despite the operation itself being non-destructive.
From the tool's definition Tool name 'get_bridge_status' and description 'Check status of cross-chain bridges' indicate a query operation that retrieves bridge status information without modification.
Attacks that exploit this kind of access
Check status of cross-chain bridges. It is categorised as a Read tool in the JS-Peer x DeFi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JS-Peer x DeFi MCP Server MCP server in PolicyLayer and add a rule for get_bridge_status: 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 JS-Peer x DeFi MCP Server. Nothing to install.
get_bridge_status 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 get_bridge_status 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 get_bridge_status. 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.
get_bridge_status is provided by the JS-Peer x DeFi MCP Server MCP server (nkovaturient/js-peer-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 →