This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/random-uuid.md
What random_uuid does on UnClick
AI agents call random_uuid as a supporting operation in UnClick workflows.
Why random_uuid is rated Low
This tool simply generates a random UUID locally. It does not read, write, execute, delete, or move money. It has no side effects and no blast radius if misused — it just produces a random identifier string.
From the tool's definition Generate a random UUID
Attacks that exploit this kind of access
The rule that runs random_uuid 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_uuid, this is the rule to start with:
random_uuid gets a rate cap, and 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_uuid call is checked against it from then on.
Questions about random_uuid
Generate a random UUID. It is categorised as a Other tool in the UnClick MCP Server, which means it performs auxiliary operations.
Register the UnClick MCP server in PolicyLayer and add a rule for random_uuid: 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_uuid is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the random_uuid 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_uuid. 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_uuid 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