This record as markdown: /tools/io-tinyfn-tinyfn/random-time.md
What random_time does on TinyFn
AI agents call random_time 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 times to generate |
format | string | — | Output format: 24h, 12h, iso |
include_seconds | boolean | — | Include seconds in output |
Parameters from the server's own tool schema.
Why random_time is rated Low
The tool produces random time values deterministically based on its algorithm. It does not modify any data, execute external code, delete anything, or involve financial transactions. It fits cleanly into the Read category as a data generation utility with no capability to cause harm if misused by an AI agent.
From the tool's definition Tool is described as generating random time(s) of day. This is a pure computation that retrieves/generates data with no side effects, no state modification, no execution of external operations, and no destructive or financial impact.
Attacks that exploit this kind of access
The rule that runs random_time 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_time, this is the rule to start with:
random_time 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_time call is checked against it from then on.
Questions about random_time
Generate random time(s) of day. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_time accepts 3 parameters: count, format, include_seconds. 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_time: 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_time 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_time 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_time. 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_time 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