New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

frantic.set_payout

Set or update the x402 wallet where the operator is paid, via PATCH /v1/agents/{kid}/payout. Safe to re-run anytime: the newest call replaces the wallet on file, so a wrong address is corrected by calling it again with the right one (no manual fix needed). The venue stores only a hash and a maske...

SERVERFrantic SOURCEhttps://api.gofrantic.com/mcp
Critical RISK CLASS
Category Financial
Parameters 44 required
Recommended Approval-gatedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gofrantic-frantic/frantic.set-payout.md

What frantic.set_payout does on Frantic

AI agents use frantic.set_payout to commit financial operations through Frantic, usually the final step of a payment, billing, or trading workflow. A call moves real money.

ParameterTypeRequiredDescription
rail string Yes Payout rail: x402, the wallet rail.
target string Yes Payout target: a 0x base address for the x402 rail. Re-running with a new target replaces the wallet on file. The venue stores only a hash and a masked hint.
agent_kid string Yes Public agent key id.
agent_token string Yes Private agent token.

Parameters from the server's own tool schema.

Why frantic.set_payout is rated Critical

This tool modifies where money is sent (the payout wallet address), which is a financial operation. Misuse by an AI agent could redirect operator payments to an attacker-controlled wallet. While it doesn't directly move funds, it controls the destination of financial flows, making it Financial in category.

From the tool's definition 'Set or update the x402 wallet where the operator is paid' and 'PATCH /v1/agents/{kid}/payout' — this tool controls the destination wallet for financial payouts

Questions about frantic.set_payout

What does the frantic.set_payout tool do? +

Set or update the x402 wallet where the operator is paid, via PATCH /v1/agents/{kid}/payout. Safe to re-run anytime: the newest call replaces the wallet on file, so a wrong address is corrected by calling it again with the right one (no manual fix needed). The venue stores only a hash and a masked hint, never the raw address. Stripe payouts go through the operator payout onboarding, not this tool. It is categorised as a Financial tool in the Frantic MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does frantic.set_payout accept? +

frantic.set_payout accepts 4 parameters: rail, target, agent_kid, agent_token. Required: rail, target, agent_kid, agent_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on frantic.set_payout? +

Register the Frantic MCP server in PolicyLayer and add a rule for frantic.set_payout: 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 Frantic. Nothing to install.

What risk level is frantic.set_payout? +

frantic.set_payout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit frantic.set_payout? +

Yes. Add a rate_limit block to the frantic.set_payout 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.

How do I block frantic.set_payout completely? +

Set action: deny in the PolicyLayer policy for frantic.set_payout. 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.

What MCP server provides frantic.set_payout? +

frantic.set_payout is provided by the Frantic MCP server (https://api.gofrantic.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Frantic, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Frantic's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.