Notify the Relay backend about a transaction. This is used to index and track transactions for cross-chain operations.\n\nWhen to use:\n• After executing a transaction from a quote response\n• When you want Relay to track a specific transaction\n• For proper status monitoring and request linking\...
AI agents use relay_transactions_index to create or update resources in Relay Protocol MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Relay Protocol MCP Server environment.
This tool writes/registers transaction data to the Relay backend for tracking purposes. It creates a record linking a transaction hash and chain ID for monitoring. It does not execute transactions, move funds, or delete data — it simply notifies and registers an existing transaction for indexing.
From the tool's definition 'Notify the Relay backend about a transaction... used to index and track transactions for cross-chain operations'
Attacks that exploit this kind of access
Notify the Relay backend about a transaction. This is used to index and track transactions for cross-chain operations.\n\nWhen to use:\n• After executing a transaction from a quote response\n• When you want Relay to track a specific transaction\n• For proper status monitoring and request linking\n\nExample: After sending the deposit transaction from relay_get_quote response, call this tool with the transaction hash and chain ID to enable proper tracking.\n\nRequired: txHash (0x...), chainId (number)\nOptional: requestId (from quote response for linking). It is categorised as a Write tool in the Relay Protocol MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Relay Protocol MCP Server MCP server in PolicyLayer and add a rule for relay_transactions_index: 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_transactions_index is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the relay_transactions_index 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_transactions_index. 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_transactions_index 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 →