Critical Risk →

play

One-shot autonomous playbook. The ONLY tool a stateless agent loop needs. WHAT IT DOES: collapses the typical play cycle into a single call: 1. get_me to check SOL/$fomox402 balances. 2. If SOL < min_sol_lamports, call topup (silently swallowing rate-limits). 3. list_games, filter to live rounds ...

Risk signalsHandles credentials or secrets (api_key)

Part of the Fomox402 server.

play can permanently delete data in Fomox402, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FOMOX402 →

Free to start. No card required.

AI agents may call play to permanently remove or destroy resources in Fomox402. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call play in a loop, permanently destroying resources in Fomox402. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "play"
  ]
}

See the full Fomox402 policy for all 25 tools.

Get this rule live on your own Fomox402 server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FOMOX402 →

View all 25 tools →

These attack patterns abuse exactly the kind of access play gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so play only ever does what you allow.

SECURE FOMOX402 →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the play tool do? +

One-shot autonomous playbook. The ONLY tool a stateless agent loop needs. WHAT IT DOES: collapses the typical play cycle into a single call: 1. get_me to check SOL/$fomox402 balances. 2. If SOL < min_sol_lamports, call topup (silently swallowing rate-limits). 3. list_games, filter to live rounds (gameOver=false, deadline > now+10s), sort by tokenPot desc, pick highest. 4. If you're already the head bidder AND deadline > sit_if_head_threshold_sec in the future → don't bid, return status='sit_holding_head'. 5. Else place_bid at effective_min + 1 raw via the full x402 flow. Returns one structured status object with everything that happened, so prompt-style agents can run on a 30–60s cron without holding any state. WHEN TO USE: as the only tool in a recurring agent loop. Drop into Claude Desktop / Cursor / Goose / a cron job and run forever. Equivalent to the autonomous-mode flow described in the server-level instructions. POSSIBLE STATUSES (in returned JSON): 'no_live_games' — nothing biddable; just wait and try again 'sit_holding_head' — you're winning, no action needed 'bid_landed' — bid placed (x402_paid true/false depending on flow) And error statuses if any sub-step fails: play_get_me_failed, play_list_games_failed, play_x402_pay_failed, play_bid_first_leg_failed, play_bid_second_leg_failed, play_402_no_nonce. RETURNS: { status, gameId?, amountRaw?, x402_paid?, x402_fee_tx?, tx?, topup? (sub-result of any topup attempt), timer_remaining_sec?, note? }. RELATED: get_me, list_games, place_bid, topup, claim_winnings — call those individually if you want fine-grained control.. It is categorised as a Destructive tool in the Fomox402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on play? +

Register the Fomox402 MCP server in PolicyLayer and add a rule for play: 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.

What risk level is play? +

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

Can I rate-limit play? +

Yes. Add a rate_limit block to the play 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 play completely? +

Set action: deny in the PolicyLayer policy for play. 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 play? +

play 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.

Enforce policy on every Fomox402 tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.