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.
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.
Documented attack patterns abuse exactly the kind of access send_batch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for send_batch:
{
"version": "1",
"default": "deny",
"tools": {
"send_batch": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to send_batch is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
send_batch. 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.
Start from Waiaas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.