Notify the Relay backend to index transfers, wraps and unwraps for a specific transaction.\n\nWhen to use:\n• Index specific transfers within a transaction\n• Track wrap/unwrap operations\n• Associate transaction data with a request ID\n\nDifference from relay_transactions_index:\n• This is for i...
AI agents use relay_transactions_single 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 indexing purposes. It creates or updates records associating a transaction hash with transfers and wrap/unwrap operations. While it involves cross-chain financial infrastructure, the tool itself does not move money or commit financial obligations — it only notifies/registers existing transaction data for tracking.
From the tool's definition Notify the Relay backend to index transfers, wraps and unwraps for a specific transaction
Attacks that exploit this kind of access
Notify the Relay backend to index transfers, wraps and unwraps for a specific transaction.\n\nWhen to use:\n• Index specific transfers within a transaction\n• Track wrap/unwrap operations\n• Associate transaction data with a request ID\n\nDifference from relay_transactions_index:\n• This is for indexing specific transfers/wraps/unwraps\n• relay_transactions_index is for general transaction tracking\n\nRequired: requestId, chainId (string), tx (transaction hash). 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_single: 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_single 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_single 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_single. 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_single 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 →