Tip a harness author in USDC over x402. Returns the payable endpoint and its payment details — GET it with an x402-capable client/wallet to actually send the tip (the agent's own wallet pays; Loadbay never holds funds).
AI agents use tip_harness 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 |
|---|---|---|---|
slug | string | Yes | the harness slug to tip |
amount | number | — | tip amount in USD (default 1); the author receives USDC |
Parameters from the server's own tool schema.
This tool initiates a financial transaction — sending USDC cryptocurrency from the agent's wallet to a harness author. Even though it returns a payable endpoint rather than directly executing the payment, it is explicitly designed to facilitate and trigger a real monetary transfer. The agent's own wallet bears the cost, making misuse a direct financial risk. Financial category applies as it moves money (USDC tips).
From the tool's definition Tip a harness author in USDC over x402... the agent's own wallet pays
Attacks that exploit this kind of access
Tip a harness author in USDC over x402. Returns the payable endpoint and its payment details — GET it with an x402-capable client/wallet to actually send the tip (the agent's own wallet pays; Loadbay never holds funds). 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.
tip_harness accepts 2 parameters: slug, amount. Required: slug. 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 tip_harness: 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.
tip_harness 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 tip_harness 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 tip_harness. 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.
tip_harness 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.
tip_harness 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 →