random_date
Generate random date(s) within a range.
This record as markdown: /tools/io-tinyfn-tinyfn/random-date.md
What random_date does on TinyFn
AI agents call random_date 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 |
|---|---|---|---|
end | string | — | End date (YYYY-MM-DD) |
count | integer | — | Number of dates to generate |
start | string | — | Start date (YYYY-MM-DD) |
format | string | — | Output format: iso, us, eu, unix |
Parameters from the server's own tool schema.
Why random_date is rated Low
This tool retrieves/generates data (random dates) with no capability to modify, execute commands, delete resources, or affect financial systems. The 'Generate' verb here means computational generation of values, not creation of persistent artifacts. It is a pure utility function typical of a math/conversion/date-time tool library, with minimal blast radius if misused by an AI agent.
From the tool's definition Tool 'random_date' generates random date(s) within a range. The description indicates a deterministic utility function that produces output data without side effects, persistent state modification, or external operations.
Attacks that exploit this kind of access
The rule that runs random_date 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 random_date, this is the rule to start with:
random_date 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 random_date call is checked against it from then on.
Questions about random_date
Generate random date(s) within a range. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_date accepts 4 parameters: end, count, start, format. 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 random_date: 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.
random_date 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 random_date 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_date. 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_date 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