date_diff

Calculate difference between two dates.

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

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-tinyfn-tinyfn/date-diff.md

WHAT IT DOES

What date_diff does on TinyFn

AI agents call date_diff 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
`date1`	string	Yes	First date (ISO format)
`date2`	string	Yes	Second date (ISO format)

Parameters from the server's own tool schema.

RISK

Why date_diff is rated Low

This is a deterministic mathematical utility that reads input date values and returns a computed difference. It performs no writes, deletions, code execution, or financial transactions. As part of a suite of math and conversion tools, it represents a safe read-only operation with minimal security risk.

From the tool's definition Tool name 'date_diff' and description 'Calculate difference between two dates' indicate a pure calculation/query operation with no side effects, data modification, or external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

date_diff Allowed

date_diff 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": {
    "date_diff": {}
  }
}

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 date_diff call is checked against it from then on.

FAQ

Questions about date_diff

What does the date_diff tool do? +

Calculate difference between two dates. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.

What parameters does date_diff accept? +

date_diff accepts 2 parameters: date1, date2. Required: date1, date2. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on date_diff? +

Register the TinyFn MCP server in PolicyLayer and add a rule for date_diff: 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 date_diff? +

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

Can I rate-limit date_diff? +

Yes. Add a rate_limit block to the date_diff 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 date_diff completely? +

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

date_diff 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 →