Transfer USDC between master account and sub-account
AI agents use hl_sub_transfer to commit financial operations through Waiaas — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money (USDC tokens) between accounts, which is a direct financial transaction. Even with the policy engine and spending limits mentioned in the server description, the tool's core function is to commit financial obligations and transfer value. This is the most severe risk category. The confidence is high because the description unambiguously describes a token transfer operation.
From the tool's definition Tool description explicitly states 'Transfer USDC between master account and sub-account'. USDC is a stablecoin with direct financial value.
Documented attack patterns abuse exactly the kind of access hl_sub_transfer 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 hl_sub_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"hl_sub_transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to hl_sub_transfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer USDC between master account and sub-account. 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 hl_sub_transfer: 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.
hl_sub_transfer 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 hl_sub_transfer 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 hl_sub_transfer. 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.
hl_sub_transfer 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.