Get the current execution status of a cross-chain request. Returns status, transaction hash, and other execution details.\n\nWhen to use: After executing a quote/swap, use the requestId from the response to monitor progress.\nRequest ID format: Hex string starting with
AI agents call relay_get_execution_status to retrieve information from Relay Protocol 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 monitoring/query tool that retrieves the status of previously-executed cross-chain requests. It only reads and returns execution details without modifying state, executing new transactions, or moving funds. While it operates in a financial domain (blockchain/DeFi), the tool itself performs no financial transactions or state-changing operations.
From the tool's definition Tool description states it 'Get[s] the current execution status' and 'Returns status, transaction hash, and other execution details.' The verb 'get' and focus on returning/retrieving information indicates a read operation with no side effects.
Attacks that exploit this kind of access
Get the current execution status of a cross-chain request. Returns status, transaction hash, and other execution details.\n\nWhen to use: After executing a quote/swap, use the requestId from the response to monitor progress.\nRequest ID format: Hex string starting with. It is categorised as a Read tool in the Relay Protocol MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay Protocol MCP Server MCP server in PolicyLayer and add a rule for relay_get_execution_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 Relay Protocol MCP Server. Nothing to install.
relay_get_execution_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 relay_get_execution_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 relay_get_execution_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.
relay_get_execution_status is provided by the Relay Protocol MCP Server MCP server (warengonzaga/relay-protocol-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 →