broadcast_transaction
Broadcast a pre-signed Stacks transaction to the network.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/broadcast-transaction.md
What broadcast_transaction does on Aibtc
AI agents invoke broadcast_transaction to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why broadcast_transaction is rated High
Broadcasting a signed transaction to a blockchain network is an irreversible external operation that triggers on-chain effects. It cannot be undone once submitted. While it could potentially involve financial transfers, the tool itself only broadcasts a pre-signed transaction (the signing happens elsewhere), so it's best classified as Execute with high severity due to the irreversible on-chain impact.
From the tool's definition Broadcast a pre-signed Stacks transaction to the network
Attacks that exploit this kind of access
The rule that runs broadcast_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For broadcast_transaction, this is the rule to start with:
broadcast_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every broadcast_transaction call is checked against it from then on.
Questions about broadcast_transaction
Broadcast a pre-signed Stacks transaction to the network. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aibtc MCP server in PolicyLayer and add a rule for broadcast_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 Aibtc. Nothing to install.
broadcast_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the broadcast_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.
Set action: deny in the PolicyLayer policy for broadcast_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.
broadcast_transaction is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue