// SCAN REPORT

Base Batch Send

4 tools. 3 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

3 can modify or destroy data

1 read-only

4 tools total

Community server · catalogue entry verified 30/06/2026

How to control Base Batch Send ↓

TOOL MAP

What Base Batch Send exposes to your agents

Read (1) Write / Execute (1) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Base Batch Send tools

Financial · Critical batch_send_erc20 This tool moves cryptocurrency assets (ERC-20 tokens) to multiple recipients and charges a fee in ETH, constituting a direct financial transaction. Financial · Critical batch_send_eth This tool directly transfers cryptocurrency (ETH) to multiple recipients on the Base blockchain, which constitutes an irreversible financial transaction. Write · Medium estimate_batch Estimate gas cost and total ETH needed for a batch send operation. Use before executing to verify costs.

3 of Base Batch Send's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Base Batch Send

PolicyLayer is an MCP gateway — it sits between your AI agents and Base Batch Send, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "batch_send_erc20": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "estimate_batch": {
    "limits": [
      {
        "counter": "estimate_batch_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_batch_info": {
    "limits": [
      {
        "counter": "get_batch_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Base Batch Send — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BASE BATCH SEND →

Instant setup, no code required.

FULL CATALOGUE

All 4 Base Batch Send tools

FINANCIAL 2 tools

Financial batch_send_erc20 Send ERC-20 tokens to multiple recipients in a single transaction on Base. Automatically handles token approva Financial batch_send_eth Send ETH to multiple recipients in a single transaction on Base. Requires DEPLOYER_PRIVATE_KEY env var. A smal

WRITE 1 tools

Write estimate_batch Estimate gas cost and total ETH needed for a batch send operation. Use before executing to verify costs.

READ 1 tools

Read get_batch_info Get BatchSender contract info — current fee, treasury address, contract address. Use to verify the contract is

FAQ

Questions about Base Batch Send

Can an AI agent move money through the Base Batch Send MCP server? +

Yes. The Base Batch Send server exposes 2 financial tools including batch_send_erc20, batch_send_eth. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Base Batch Send? +

The Base Batch Send server has 1 write tools including estimate_batch. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Base Batch Send.

How many tools does the Base Batch Send MCP server expose? +

4 tools across 2 categories: Read, Write. 1 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Base Batch Send? +

Register the Base Batch Send MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Base Batch Send tool call.

Deterministic rules across all 4 Base Batch Send tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BASE BATCH SEND →

Instant setup, no code required.

4 Base Batch Send tools catalogued and risk-classified — across an index of 43,000+ MCP servers.