generate_dates · TinyFn MCP: Risk & Policy

WHAT IT DOES

What generate_dates does on TinyFn

AI agents use generate_dates 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 dates
`format`	string	—	Format: ISO, US, EU
`end_year`	integer	—	End year
`start_year`	integer	—	Start year

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why generate_dates needs a policy

An AI agent can call generate_dates faster than any human can review — one bad instruction and it creates or modifies resources in TinyFn by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_dates Rate-limited

generate_dates 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_dates": {
      "limits": [
        {
          "counter": "generate_dates_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_dates

What does the generate_dates tool do? +

Generate random dates. 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_dates accept? +

generate_dates accepts 4 parameters: count, format, end_year, start_year. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_dates? +

Register the TinyFn MCP server in PolicyLayer and add a rule for generate_dates: 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_dates? +

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

Can I rate-limit generate_dates? +

Yes. Add a rate_limit block to the generate_dates 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_dates completely? +

Set action: deny in the PolicyLayer policy for generate_dates. 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_dates? +

generate_dates 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.