This record as markdown: /tools/creativelead-unclick/random-uuid.md
What random_uuid does on UnClick
AI agents call random_uuid 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.
Why random_uuid is rated Low
UUID generation is a deterministic cryptographic operation with no side effects, no data access, no external operations triggered, and no ability to modify or delete anything. It is a simple read-only utility function that returns a computed value. This is the lowest risk category.
From the tool's definition Tool name is 'random_uuid' and description states 'Generate a random UUID.' This is a pure utility function that generates a random identifier with no data retrieval, modification, execution, or side effects.
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 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_uuid call is checked against it from then on.
Questions about random_uuid
Generate a random UUID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
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 Read 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 (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