This record as markdown: /tools/io-tinyfn-tinyfn/date-to-timestamp.md
What date_to_timestamp does on TinyFn
AI agents call date_to_timestamp 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 |
|---|---|---|---|
date | string | Yes | Date string (YYYY-MM-DD or ISO format) |
Parameters from the server's own tool schema.
Why date_to_timestamp is rated Low
Date-to-timestamp conversion is a deterministic mathematical transformation. It retrieves a computed value without creating, modifying, deleting, or executing anything external. The tool belongs in the Read category. Severity is low because misuse would only return incorrect timestamp values, causing no blast radius to systems or data.
From the tool's definition Tool name is 'date_to_timestamp' and description states 'Convert date to Unix timestamp.' This is a pure data conversion operation that reads/retrieves a timestamp value based on input date, with no side effects, data modification, execution of code, or…
Attacks that exploit this kind of access
The rule that runs date_to_timestamp 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 date_to_timestamp, this is the rule to start with:
date_to_timestamp 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 date_to_timestamp call is checked against it from then on.
Questions about date_to_timestamp
Convert date to Unix timestamp. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
date_to_timestamp accepts 1 parameter: date. Required: date. 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 date_to_timestamp: 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.
date_to_timestamp 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 date_to_timestamp 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 date_to_timestamp. 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.
date_to_timestamp 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