Support the Loadbay builder with a USDC tip over x402. Returns the payable endpoint — GET it with your own x402 wallet to send the tip. Loadbay never holds funds; your wallet is the payer.
AI agents use support_loadbay to commit financial operations through Loadbay — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | — | tip amount in USD (default 5); the builder receives USDC |
Parameters from the server's own tool schema.
This tool initiates a financial transaction — sending USDC cryptocurrency as a tip via the x402 payment protocol. Even though it returns a payable endpoint rather than directly executing the payment, its explicit purpose is to commit funds, placing it firmly in the Financial category. Misuse by an AI agent could result in unauthorized monetary transfers.
From the tool's definition Support the Loadbay builder with a USDC tip over x402... GET it with your own x402 wallet to send the tip
Attacks that exploit this kind of access
Support the Loadbay builder with a USDC tip over x402. Returns the payable endpoint — GET it with your own x402 wallet to send the tip. Loadbay never holds funds; your wallet is the payer. It is categorised as a Financial tool in the Loadbay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
support_loadbay accepts 1 parameter: amount. The full parameter table on this page comes from the server's own tool schema.
Register the Loadbay MCP server in PolicyLayer and add a rule for support_loadbay: 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 Loadbay. Nothing to install.
support_loadbay 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 support_loadbay 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 support_loadbay. 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.
support_loadbay is provided by the Loadbay MCP server (https://loadbay.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
support_loadbay is one line of Loadbay's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →