This record as markdown: /tools/io-tinyfn-tinyfn/add-time.md
What add_time does on TinyFn
AI agents use add_time 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | Yes | Start date (ISO format) |
days | integer | — | Days to add |
hours | integer | — | Hours to add |
weeks | integer | — | Weeks to add |
minutes | integer | — | Minutes to add |
seconds | integer | — | Seconds to add |
Parameters from the server's own tool schema.
Why add_time is rated Medium
This tool creates or modifies date/time values by adding a time interval to a date, which is a reversible write operation. It does not delete, execute arbitrary code, or access external systems. The blast radius is minimal since it only performs deterministic temporal arithmetic without persistent side effects or state changes in external systems.
From the tool's definition Tool name 'add_time' and description 'Add time to a date' indicates modification of temporal data. The verb 'Add' and action of modifying a date value by adding time to it constitutes data transformation.
Attacks that exploit this kind of access
The rule that runs add_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 add_time, this is the rule to start with:
add_time 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.
The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every add_time call is checked against it from then on.
Questions about add_time
Add time to a date. 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.
add_time accepts 6 parameters: date, days, hours, weeks, minutes, seconds. 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 add_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.
add_time is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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