AI agents use send_token to commit financial operations through Waiaas — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Even though the description is empty, the tool name 'send_token' on a crypto wallet MCP server strongly implies transferring cryptocurrency or tokens to another address. This constitutes a financial operation that moves crypto assets, potentially irreversibly. The server context confirms this is a wallet server for multi-chain crypto operations including transfers.
From the tool's definition Tool name 'send_token' 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 explicit mention of 'transfers'.
Documented attack patterns abuse exactly the kind of access send_token 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_token:
{
"version": "1",
"default": "deny",
"tools": {
"send_token": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to send_token is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
send_token. 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_token: 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_token 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_token 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_token. 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_token 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.