batch_tx_info

THE RISK

Low Risk

Why batch_tx_info needs a policy

This tool retrieves historical transaction data and statistics for multiple tokens without modifying blockchain state, executing trades, moving funds, or triggering external operations. It is a read-only query operation consistent with other data retrieval tools on the server (balance, batch_token_info, coin_market_info, kline, holders_info).

From the tool's definition Tool name and description indicate batch retrieval of transaction statistics: 'Batch get transaction statistics for multiple tokens.' The verb 'get' and 'statistics' indicate data querying with no modification, deletion, or execution of transactions.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control batch_tx_info

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_tx_info": {}
  }
}

batch_tx_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Bitget Wallet 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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bitget Wallet MCP Server tools

Financial transfer_make_order transfer_make_order Financial transfer_submit transfer_submit Execute swap_confirm swap_confirm Execute swap_make_order swap_make_order Execute swap_quote swap_quote Execute swap_send Submit signed transactions for a swap order. Read security_audit Run a security audit on a token contract (honeypot detection, permission checks, blacklist Read balance balance

All 39 Bitget Wallet MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about batch_tx_info

What does the batch_tx_info tool do? +

Batch get transaction statistics for multiple tokens. It is categorised as a Read tool in the Bitget Wallet MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on batch_tx_info? +

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

What risk level is batch_tx_info? +

batch_tx_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit batch_tx_info? +

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

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

batch_tx_info is provided by the Bitget Wallet MCP Server MCP server (bitget-wallet-ai-lab/bitget-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bitget Wallet MCP Server tool call.

Start from Bitget Wallet 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 →