random_draw
Provably fair random draws for giveaways, raffles, games and A/B assignment. Pick winners from a list (unique or with replacement, optional weights), shuffle a list, split people into balanced teams, draw integers in a range, or roll dice ("3d6+2", "4d6kh3"). Randomness is HMAC-SHA256(serverSeed,...
This record as markdown: /tools/com-it-scorptech-x402/random-draw.md
What random_draw does on ScorpTech x402 API
AI agents invoke random_draw to trigger actions in ScorpTech x402 API. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
max | integer | — | |
min | integer | — | |
dice | string | — | Dice notation: NdS(+/-M), kh/kl to keep highest / lowest, e.g. "4d6kh3", "2d20kl1", "3d6+2" |
mode | string | — | |
count | integer | — | Winners (pick), numbers (integers), teams (teams) |
items | array | — | Entries (strings / numbers / objects) for pick, shuffle, teams; max 10,000 |
nonce | integer | — | |
unique | boolean | — | pick / integers without replacement |
weights | array | — | pick: non-negative weight per item (with unique=true, weighted sampling without replacement) |
clientSeed | string | — | Your seed (e.g. a public value fixed before the draw) |
serverSeed | string | — | Verification: re-run a draw with its published server seed (hex) |
Parameters from the server's own tool schema.
Why random_draw is rated High
random_draw triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs random_draw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For random_draw, this is the rule to start with:
random_draw stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every random_draw call is checked against it from then on.
Questions about random_draw
Provably fair random draws for giveaways, raffles, games and A/B assignment. Pick winners from a list (unique or with replacement, optional weights), shuffle a list, split people into balanced teams, draw integers in a range, or roll dice ("3d6+2", "4d6kh3"). Randomness is HMAC-SHA256(serverSeed, clientSeed:nonce:counter) with unbiased rejection sampling and Fisher–Yates; the response publishes the server seed, its SHA-256 commitment and the algorithm so anyone can re-run and verify the draw. Supply serverSeed + clientSeed to reproduce a previous draw exactly. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/random-draw. It is categorised as a Execute tool in the ScorpTech x402 API MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
random_draw accepts 11 parameters: max, min, dice, mode, count, items, nonce, unique, weights, clientSeed, serverSeed. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for random_draw: 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 ScorpTech x402 API. Nothing to install.
random_draw is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the random_draw 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 random_draw. 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.
random_draw is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue