Medium Risk

send_raw_transaction

Submit signed transactions to the Algorand network

How to control send_raw_transaction ↓

AI agents use send_raw_transaction to create or update resources in BNB Chain MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BNB Chain MCP environment.

Medium Risk

An AI agent can call send_raw_transaction faster than any human can review — one bad instruction and it creates or modifies resources in BNB Chain MCP by the hundred, each call as confident as the last.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_raw_transaction": {
      "limits": [
        {
          "counter": "send_raw_transaction_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

send_raw_transaction stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the send_raw_transaction tool do? +

Submit signed transactions to the Algorand network. It is categorised as a Write tool in the BNB Chain MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_raw_transaction? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for send_raw_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 BNB Chain MCP. Nothing to install.

What risk level is send_raw_transaction? +

send_raw_transaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_raw_transaction? +

Yes. Add a rate_limit block to the send_raw_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 send_raw_transaction completely? +

Set action: deny in the PolicyLayer policy for send_raw_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 send_raw_transaction? +

send_raw_transaction is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.