Settle a finished round and pay out the winner. WHAT IT DOES: invokes the Anchor program's claim instruction, which atomically distributes the pot per the round's split bps: winnerBps → last bidder (the winner) creatorBps → round creator refsBps → winner's referrer (if set) devBps → staccpad.fun ...
Risk signalsHandles credentials or secrets (api_key)
Part of the Fomox402 server.
Free to start. No card required.
AI agents use claim_winnings to create or modify resources in Fomox402. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call claim_winnings repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Fomox402.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"claim_winnings": {
"limits": [
{
"counter": "claim_winnings_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Fomox402 policy for all 25 tools.
These attack patterns abuse exactly the kind of access claim_winnings gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Settle a finished round and pay out the winner. WHAT IT DOES: invokes the Anchor program's claim instruction, which atomically distributes the pot per the round's split bps: winnerBps → last bidder (the winner) creatorBps → round creator refsBps → winner's referrer (if set) devBps → staccpad.fun dev wallet Marks the round gameOver=true so list_games filters it out. WHEN TO USE: after a round's deadline has passed (deadline ≤ now) and the round is not yet gameOver. The broker also runs an autoclaim worker that calls this on your behalf within ~30s of expiry, so manual claims are an optimization, not a requirement. PERMISSIONLESS: anyone can call claim_winnings on any expired round — the on-chain program routes the funds correctly regardless of who pays the tx fee. So if you're the winner and the auto-claim worker is slow, just call this yourself. RETURNS: { tx (Solana sig), gameId, payouts: { winner: { address, amountRaw }, creator: {...}, ref?: {...}, dev: {...} } }. FAILURE MODES: claim_failed (not_expired) — deadline hasn't passed yet claim_failed (already_claimed) — round was already settled (gameOver) claim_failed (rpc) — Solana RPC issue, retry in a few seconds RELATED: claim_dividend (the per-key share — separate from this winner payout), get_game (verify deadline), play (auto-handles winner check).. It is categorised as a Write tool in the Fomox402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fomox402 MCP server in PolicyLayer and add a rule for claim_winnings: 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 Fomox402. Nothing to install.
claim_winnings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the claim_winnings 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 claim_winnings. 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.
claim_winnings is provided by the Fomox402 MCP server (https://bot.staccpad.fun/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Fomox402 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.