This record as markdown: /tools/creativelead-unclick/random-string.md
What random_string does on UnClick
AI agents call random_string 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 |
|---|---|---|---|
length | number | — | |
charset | string | — |
Parameters from the server's own tool schema.
Why random_string is rated Low
This is a utility function that produces randomized output without reading, writing, executing, or destructive operations. It has no blast radius if misused by an AI agent, as the output is inert data with no downstream effects on external systems or data stores.
From the tool's definition Tool name and description indicate it 'Generate a random string' - a pure data generation function with no side effects, no data retrieval, no external operations, and no modifications to any system state.
Attacks that exploit this kind of access
The rule that runs random_string 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_string, this is the rule to start with:
random_string 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_string call is checked against it from then on.
Questions about random_string
Generate a random string. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
random_string accepts 2 parameters: length, charset. 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_string: 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_string 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_string 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_string. 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_string is provided by the UnClick MCP server (creativelead/unclick). 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