This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-number.md
What random_number does on UnClick
AI agents call random_number to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
max | number | — | |
min | number | — | |
count | number | — | |
integer | boolean | — |
Parameters from the server's own tool schema.
Why random_number is rated Low
This is a stateless computation tool that returns a value without querying, modifying, deleting, or executing external systems. It has no blast radius if misused by an AI agent, as it cannot affect data, systems, or financial transactions. Categorized as Read (computation with no side effects) rather than Other, as it still produces deterministic output within specified parameters.
From the tool's definition Tool generates a random number within a range with no side effects, data retrieval, or external operations. The description indicates a pure computation function: 'Generate a random number within a range.'
Attacks that exploit this kind of access
The rule that runs random_number safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For random_number, this is the rule to start with:
random_number is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every random_number call is checked against it from then on.
Questions about random_number
Generate a random number within a range. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
random_number accepts 4 parameters: max, min, count, integer. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for random_number: 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 UnClick. Nothing to install.
random_number is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the random_number 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_number. 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_number is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue