moonpay_sign_onramp_url
Build a signed MoonPay widget URL for an agent or user to complete the on-ramp in their browser. The signature binds wallet address + amount + currency so the params cannot be tampered with after generation.
This record as markdown: /tools/market-execution-execution-market/moonpay-sign-onramp-url.md
What moonpay_sign_onramp_url does on Execution Market
AI agents use moonpay_sign_onramp_url to commit financial operations through Execution Market, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why moonpay_sign_onramp_url is rated Critical
This tool generates a cryptographically signed URL that initiates a MoonPay on-ramp transaction, committing financial parameters (wallet address, amount, currency). While the user still completes the flow in a browser, the signing step binds the financial terms and enables a real-money purchase, placing it squarely in the Financial category.
From the tool's definition 'signed MoonPay widget URL for an agent or user to complete the on-ramp' and 'Gasless USDC payments via x402' — initiates a fiat-to-crypto on-ramp flow binding wallet address + amount + currency
Attacks that exploit this kind of access
The rule that runs moonpay_sign_onramp_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Execution Market, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For moonpay_sign_onramp_url, this is the rule to start with:
Any call to moonpay_sign_onramp_url is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every moonpay_sign_onramp_url call is checked against it from then on.
Questions about moonpay_sign_onramp_url
Build a signed MoonPay widget URL for an agent or user to complete the on-ramp in their browser. The signature binds wallet address + amount + currency so the params cannot be tampered with after generation. It is categorised as a Financial tool in the Execution Market MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Execution Market MCP server in PolicyLayer and add a rule for moonpay_sign_onramp_url: 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 Execution Market. Nothing to install.
moonpay_sign_onramp_url 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 moonpay_sign_onramp_url 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 moonpay_sign_onramp_url. 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.
moonpay_sign_onramp_url is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Execution Market, and thousands of servers like it.
Across the catalogue