rpc_submit_transaction

THE RISK

High Risk

Why rpc_submit_transaction needs a policy

Submitting a transaction to the Bitcoin network is an irreversible external operation: once broadcast, a transaction cannot be recalled. It triggers real on-chain effects (value transfer, inscription creation, etc.).

From the tool's definition 'Pushes a signed raw transaction to the network' — broadcasts an externally constructed transaction to the Bitcoin blockchain

Documented attack patterns abuse exactly the kind of access rpc_submit_transaction gives an agent:

POLICY

How to control rpc_submit_transaction

PolicyLayer is an MCP gateway — it sits between your AI agents and Maestro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rpc_submit_transaction:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rpc_submit_transaction": {
      "limits": [
        {
          "counter": "rpc_submit_transaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

rpc_submit_transaction stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Maestro MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Maestro MCP Server tools

Destructive EventManagerService_DeleteTrigger Remove a trigger Deletes a specific trigger identified by its unique \ Execute esplora_broadcast_transaction Broadcast a raw transaction to the network. The transaction should be provided as hex in t Write EventManagerService_CreateTrigger Create a new trigger Adds a trigger to a manager to listen for specific blockchain activ Write EventManagerService_UpdateTrigger Update a trigger Allows modification of a trigger Read rpc_block_range_info Fetches basic info for a contiguous block range (start and end height). Read brc20_transfer_inscriptions_by_address Returns all unspent BRC20 transfer inscriptions residing at the address. This endpoint is Read activity_by_inscription Lists all transactions that have involved the given inscription, starting from its origin Read activity_by_rune Returns all transactions where the Rune was used or transferred, beginning with the etchin

All 117 Maestro MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Maestro MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about rpc_submit_transaction

What does the rpc_submit_transaction tool do? +

Pushes a signed raw transaction to the network. It is categorised as a Execute tool in the Maestro MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rpc_submit_transaction? +

Register the Maestro MCP Server MCP server in PolicyLayer and add a rule for rpc_submit_transaction: 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 Maestro MCP Server. Nothing to install.

What risk level is rpc_submit_transaction? +

rpc_submit_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rpc_submit_transaction? +

Yes. Add a rate_limit block to the rpc_submit_transaction 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.

How do I block rpc_submit_transaction completely? +

Set action: deny in the PolicyLayer policy for rpc_submit_transaction. 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.

What MCP server provides rpc_submit_transaction? +

rpc_submit_transaction is provided by the Maestro MCP Server MCP server (maestro-org/maestro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Maestro MCP Server tool call.

Start from Maestro MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →