zeroex_swap
Fetches a 0x AllowanceHolder quote and broadcasts its transaction from the Agent wallet after contract, amount, and simulation guards pass.
This record as markdown: /tools/awesome-base-mcp/zeroex-swap.md
What zeroex_swap does on Awesome Base
AI agents use zeroex_swap to commit financial operations through Awesome Base, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why zeroex_swap is rated Critical
Executes on-chain token swap from agent wallet, committing real financial transactions.
From the tool's definition fetches 0x quote and broadcasts transaction from Agent wallet
Attacks that exploit this kind of access
The rule that runs zeroex_swap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Awesome Base, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zeroex_swap, this is the rule to start with:
Any call to zeroex_swap is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Awesome Base, apply this rule, and every zeroex_swap call is checked against it from then on.
Questions about zeroex_swap
Fetches a 0x AllowanceHolder quote and broadcasts its transaction from the Agent wallet after contract, amount, and simulation guards pass. It is categorised as a Financial tool in the Awesome Base MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Awesome Base MCP server in PolicyLayer and add a rule for zeroex_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 Awesome Base. Nothing to install.
zeroex_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 zeroex_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 zeroex_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.
zeroex_swap is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Awesome Base, and thousands of servers like it.
Across the catalogue