This record as markdown: /tools/io-tinyfn-tinyfn/generate-dates.md
What generate_dates does on TinyFn
AI agents call generate_dates to retrieve information from TinyFn 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 |
|---|---|---|---|
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 generate_dates is rated Low
The tool generates random date values locally, consistent with the server's stated purpose of '500+ deterministic tools for AI agents: math, conversion, validation, hashing, encoding, date/time.' It reads no external data and writes nothing; it simply computes and returns date outputs. Classified as Read (data generation/computation) with low severity since misuse has negligible blast radius.
From the tool's definition Generate random dates — this is a deterministic/computational operation that produces date values with no side effects, no external data retrieval, and no modifications to any system.
Attacks that exploit this kind of access
The rule that runs generate_dates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_dates, this is the rule to start with:
generate_dates 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 TinyFn, apply this rule, and every generate_dates call is checked against it from then on.
Questions about generate_dates
Generate random dates. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
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.
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.
generate_dates 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 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.
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.
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.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue