Cross-chain bridge and swap via LI.FI aggregator. Moves tokens between different chains (e.g., SOL to Base USDC)
AI agents use cross_swap 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 cryptocurrency assets across different blockchains, which constitutes a financial operation. Cross-chain transfers are irreversible and involve real monetary value. Misuse by an AI agent could result in permanent loss of funds sent to wrong addresses or chains, or unauthorized transfers of crypto assets. Financial is the most severe applicable category given it directly moves tokens/funds.
From the tool's definition Cross-chain bridge and swap via LI.FI aggregator. Moves tokens between different chains (e.g., SOL to Base USDC)
Documented attack patterns abuse exactly the kind of access cross_swap 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 cross_swap:
{
"version": "1",
"default": "deny",
"tools": {
"cross_swap": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to cross_swap is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Cross-chain bridge and swap via LI.FI aggregator. Moves tokens between different chains (e.g., SOL to Base USDC). 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 cross_swap: 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.
cross_swap 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 cross_swap 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 cross_swap. 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.
cross_swap 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.