// SCAN REPORT

Time Tools MCP Server

7 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 30/06/2026

How to control Time Tools MCP Server ↓

TOOL MAP

What Time Tools MCP Server exposes to your agents

Read (6) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Time Tools MCP Server tools

Write · Medium convert_datetime_to_unix Convert datetime time to unixtime (e.g. 2025-01-01 01:01:01 to 1746627290)

1 of Time Tools MCP Server's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Time Tools MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Time Tools MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "convert_datetime_to_unix": {
    "limits": [
      {
        "counter": "convert_datetime_to_unix_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "convert_unix_to_datetime": {
    "limits": [
      {
        "counter": "convert_unix_to_datetime_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Time Tools MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TIME TOOLS →

Instant setup, no code required.

FULL CATALOGUE

All 7 Time Tools MCP Server tools

WRITE 1 tools

Write convert_datetime_to_unix Convert datetime time to unixtime (e.g. 2025-01-01 01:01:01 to 1746627290)

READ 6 tools

Read convert_unix_to_datetime Convert unixtime to datetime time (e.g. 1746627290 to 2025-01-01 01:01:01) Read get_current_date_time Get the current date and time (e.g. 2025-01-01 01:01:01) Read get_current_date_time_iso Get ISO 8601 time. (e.g. 2025-05-07T23:03:27+09:00) Read get_elapsed_time Get the difference time between two datetimes (e.g. 2025-01-01 01:01:01 and 2025-01-02 02:02:02) Read get_timezone Get timezone (e.g. Asia/Tokyo) Read get_unixtime Get unixtime (e.g. 1746627290)

FAQ

Questions about Time Tools MCP Server

How do I prevent bulk modifications through Time Tools MCP Server? +

The Time Tools MCP Server server has 1 write tools including convert_datetime_to_unix. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Time Tools MCP Server.

How many tools does the Time Tools MCP Server MCP server expose? +

7 tools across 2 categories: Read, Write. 6 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Time Tools MCP Server? +

Register the Time Tools MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Time Tools MCP Server tool call.

Deterministic rules across all 7 Time Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TIME TOOLS →

Instant setup, no code required.

7 Time Tools MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.