uuid5
Deterministic UUID (v5 / v3) — Stable name-based UUID from a namespace and name — same inputs, same UUID (no randomness).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/uuid5.md
What uuid5 does on Gateway
AI agents call uuid5 to retrieve information from Gateway 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 |
|---|---|---|---|
name | string | Yes | Name to hash into the UUID |
version | integer | — | 5 (SHA-1, default) or 3 (MD5) |
namespace | string | — | dns/url/oid/x500 or a UUID string (default dns) |
Parameters from the server's own tool schema.
Why uuid5 is rated Low
UUID generation is a mathematical/deterministic operation that reads input parameters and returns a computed value. It does not create, modify, delete, or access persistent data; does not execute external commands; does not transfer funds. This is equivalent to a pure function call with no side effects, placing it in the Read category with low severity.
From the tool's definition Tool generates deterministic UUIDs from namespace and name inputs; explicitly described as 'no randomness' and 'same inputs, same UUID' — purely computational, no data mutation, no external effects, no side effects.
Attacks that exploit this kind of access
The rule that runs uuid5 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uuid5, this is the rule to start with:
uuid5 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 Gateway, apply this rule, and every uuid5 call is checked against it from then on.
Questions about uuid5
Deterministic UUID (v5 / v3) — Stable name-based UUID from a namespace and name — same inputs, same UUID (no randomness). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
uuid5 accepts 3 parameters: name, version, namespace. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for uuid5: 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 Gateway. Nothing to install.
uuid5 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 uuid5 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 uuid5. 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.
uuid5 is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue