Submit a confirmed spoke-chain transaction to the SODAX intent relay so it can be delivered to the destination chain. The tx must already be finalized on the source chain. Re-submitting the same tx is a no-op. For split-tx chains (Solana, Bitcoin) supply the optional data argument.
Risk signalsAccepts raw HTML/template content (data.payload)
Part of the SODAX Builders MCP server.
Free to start. No card required.
AI agents use sodax_relay_submit_tx to create or modify resources in SODAX Builders MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call sodax_relay_submit_tx repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SODAX Builders MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"sodax_relay_submit_tx": {
"limits": [
{
"counter": "sodax_relay_submit_tx_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full SODAX Builders MCP policy for all 38 tools.
These attack patterns abuse exactly the kind of access sodax_relay_submit_tx gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit a confirmed spoke-chain transaction to the SODAX intent relay so it can be delivered to the destination chain. The tx must already be finalized on the source chain. Re-submitting the same tx is a no-op. For split-tx chains (Solana, Bitcoin) supply the optional data argument.. It is categorised as a Write tool in the SODAX Builders MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SODAX Builders MCP server in PolicyLayer and add a rule for sodax_relay_submit_tx: 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 SODAX Builders MCP. Nothing to install.
sodax_relay_submit_tx 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 sodax_relay_submit_tx 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 sodax_relay_submit_tx. 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.
sodax_relay_submit_tx is provided by the SODAX Builders MCP server (https://builders.sodax.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 SODAX Builders MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.