broadcast_transaction · Stacks AI MCP Server MCP

WHAT IT DOES

What broadcast_transaction does on Stacks AI MCP Server

AI agents invoke broadcast_transaction to trigger actions in Stacks AI MCP Server. 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 IT NEEDS A POLICY

Why broadcast_transaction needs a policy

Broadcasting a raw transaction to a blockchain network is an irreversible operation that executes on-chain. It can trigger any kind of transaction including financial transfers, contract calls, or destructive operations depending on the transaction content.

From the tool's definition Broadcast a raw transaction to the network

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

broadcast_transaction Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Stacks AI MCP Server, so you can run agents against it safely.

FAQ

Questions about broadcast_transaction

What does the broadcast_transaction tool do? +

Broadcast a raw transaction to the network. It is categorised as a Execute tool in the Stacks AI 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 broadcast_transaction? +

Register the Stacks AI MCP Server 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 Stacks AI MCP Server. Nothing to install.

What risk level is broadcast_transaction? +

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

Can I rate-limit broadcast_transaction? +

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.

How do I block broadcast_transaction completely? +

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.

What MCP server provides broadcast_transaction? +

broadcast_transaction is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

broadcast_transaction is one line of Stacks AI MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →