relative_time

Get relative time description (e.g., '2 days ago').

SERVERTinyFn SOURCEhttps://api.tinyfn.io/mcp/all/

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-tinyfn-tinyfn/relative-time.md

WHAT IT DOES

What relative_time does on TinyFn

AI agents call relative_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
`date`	string	Yes	Date (ISO format)

Parameters from the server's own tool schema.

RISK

Why relative_time is rated Low

This tool retrieves and formats temporal information for display purposes. It performs no data modification, deletion, or external operations. The output is purely informational (e.g., '2 days ago'), making it a straightforward Read category tool with low severity.

From the tool's definition Tool name 'relative_time' and description 'Get relative time description' indicate a data retrieval operation that returns a formatted time string without side effects. The verb 'Get' confirms read-only behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs relative_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 relative_time, this is the rule to start with:

relative_time Allowed

relative_time is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "relative_time": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every relative_time call is checked against it from then on.

FAQ

Questions about relative_time

What does the relative_time tool do? +

Get relative time description (e.g., '2 days ago'). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.

What parameters does relative_time accept? +

relative_time accepts 1 parameter: date. Required: date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on relative_time? +

Register the TinyFn MCP server in PolicyLayer and add a rule for relative_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.

What risk level is relative_time? +

relative_time is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit relative_time? +

Yes. Add a rate_limit block to the relative_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.

How do I block relative_time completely? +

Set action: deny in the PolicyLayer policy for relative_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.

What MCP server provides relative_time? +

relative_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.

KEEP EXPLORING

More on TinyFn, and thousands of servers like it.

This server

All 572 TinyFn tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →