generate_uuid · TinyFn MCP: Risk & Policy

WHAT IT DOES

What generate_uuid does on TinyFn

AI agents use generate_uuid to create or update resources in TinyFn — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TinyFn environment.

PARAMETERS

Parameter	Type	Required	Description
`count`	integer	—	Number of UUIDs to generate
`version`	integer	—	UUID version (1 or 4)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why generate_uuid needs a policy

Generating UUIDs is a write operation because it produces new data (identifiers). However, severity is low because UUIDs are typically harmless metadata with no financial impact, no external side effects, and no ability to cause harm via misuse—an agent generating arbitrary UUIDs has minimal blast radius.

From the tool's definition Tool generates UUID(s), which creates data (unique identifiers). The verb 'generate' combined with the purpose of creating identifiers places this in the Write category—data is created and persisted, though reversibly and without destructive effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_uuid Rate-limited

generate_uuid stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_uuid": {
      "limits": [
        {
          "counter": "generate_uuid_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TinyFn, so you can run agents against it safely.

FAQ

Questions about generate_uuid

What does the generate_uuid tool do? +

Generate UUID(s). It is categorised as a Write tool in the TinyFn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does generate_uuid accept? +

generate_uuid accepts 2 parameters: count, version. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_uuid? +

Register the TinyFn MCP server in PolicyLayer and add a rule for generate_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 TinyFn. Nothing to install.

What risk level is generate_uuid? +

generate_uuid is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_uuid? +

Yes. Add a rate_limit block to the generate_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.

How do I block generate_uuid completely? +

Set action: deny in the PolicyLayer policy for generate_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.

What MCP server provides generate_uuid? +

generate_uuid is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.