Submit a signed Ethereum bundle directly to MEV SearcherNet rbuilder for inclusion. Use this after get_liquidation_waves or get_mev_feed to act on a liquidation opportunity. Bundles are forwarded to rbuilder and fanned out to Flashbots, Titan, Beaver, BuilderNet, and bloXroute relays. 100% accept...
Risk signalsHandles credentials or secrets (api_key)
Part of the MEV Intelligence server.
Free to start. No card required.
AI agents use submit_bundle to create or modify resources in MEV Intelligence. 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 submit_bundle 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 MEV Intelligence.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"submit_bundle": {
"limits": [
{
"counter": "submit_bundle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full MEV Intelligence policy for all 9 tools.
These attack patterns abuse exactly the kind of access submit_bundle 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 signed Ethereum bundle directly to MEV SearcherNet rbuilder for inclusion. Use this after get_liquidation_waves or get_mev_feed to act on a liquidation opportunity. Bundles are forwarded to rbuilder and fanned out to Flashbots, Titan, Beaver, BuilderNet, and bloXroute relays. 100% acceptance rate. Free with API key attribution (X-Api-Key header). Returns a tracking_id you can use to check submission status at /orderflow/submissions/{tracking_id}. Tip: pair with get_liquidation_waves — identify a borrower near liquidation, construct the liquidation tx, sign it, then call this tool.. It is categorised as a Write tool in the MEV Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MEV Intelligence MCP server in PolicyLayer and add a rule for submit_bundle: 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 MEV Intelligence. Nothing to install.
submit_bundle 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 submit_bundle 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 submit_bundle. 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.
submit_bundle is provided by the MEV Intelligence MCP server (https://mev.advalorem.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 MEV Intelligence 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.