This record as markdown: /tools/minhoyoo-iotrust-waiaas/send-batch.md
What send_batch does on Waiaas
AI agents use send_batch to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why send_batch is rated Critical
On a crypto wallet MCP server with tools for transfers and multi-chain operations, 'send_batch' almost certainly sends multiple crypto transactions at once. This falls under Financial as it likely moves cryptocurrency assets. The batch nature increases blast radius significantly — a misuse could drain funds across multiple transfers simultaneously. Confidence is slightly reduced due to empty description.
From the tool's definition Tool name 'send_batch' on a server described as providing 'multi-chain crypto operations: transfers, token management, DeFi (swap, lend, stake, bridge, perp)' with sibling tools like 'bridge', 'approve_token', and various DeFi operations.
Attacks that exploit this kind of access
The rule that runs send_batch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Waiaas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_batch, this is the rule to start with:
Any call to send_batch is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every send_batch call is checked against it from then on.
Questions about send_batch
send_batch is a financial tool on the Waiaas MCP server. It is categorised as a Financial tool in the Waiaas MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Waiaas MCP server in PolicyLayer and add a rule for send_batch: 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 Waiaas. Nothing to install.
send_batch is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the send_batch 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 send_batch. 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.
send_batch is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Waiaas, and thousands of servers like it.
Across the catalogue