AI agents call number_random to retrieve information from UnClick without modifying anything — 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 | — | |
type | string | — |
Parameters from the server's own tool schema.
This tool queries and returns informational content (a random number fact) with no side effects, no data modification, no code execution, and no external state changes. It is a simple read operation with minimal security risk.
From the tool's definition Tool name 'number_random' and description 'Get a random number fact' indicate a retrieval operation that returns factual data without modifying any state or triggering external operations.
Attacks that exploit this kind of access
Get a random number fact. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
number_random accepts 3 parameters: max, min, type. 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 number_random: 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.
number_random 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 number_random 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 number_random. 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.
number_random 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →