Check the status of a deBridge cross-chain order by order ID
AI agents call getOrderStatus to retrieve information from deBridge 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 passive query operation that retrieves data about an existing order without creating, modifying, deleting, or executing any actions. The tool cannot change order state, execute transactions, or produce side effects. Even in a misuse scenario, an attacker could only gather information about orders they may or may not own, with limited blast radius. Classified as Read with low severity.
From the tool's definition Tool retrieves order status information by order ID with no modification capabilities. Description states 'check the status' and server provides 'read-only access' to order status tracking.
Attacks that exploit this kind of access
Check the status of a deBridge cross-chain order by order ID. It is categorised as a Read tool in the deBridge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the deBridge MCP Server MCP server in PolicyLayer and add a rule for getOrderStatus: 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 deBridge MCP Server. Nothing to install.
getOrderStatus 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 getOrderStatus 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 getOrderStatus. 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.
getOrderStatus is provided by the deBridge MCP Server MCP server (rookiecol/debridge-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 →