AI agents call random_uuid as a supporting operation in UnClick workflows.
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
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.
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 →