current_time

Get current time in specified timezone.

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

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What current_time does on TinyFn

AI agents call current_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
`timezone_name`	string	—	Timezone name (e.g., UTC, EST, PST, JST)

Parameters from the server's own tool schema.

RISK

Why current_time is rated Low

This tool reads and returns time data without side effects. It is a straightforward query that retrieves information. The blast radius of misuse is minimal—an AI agent obtaining current time cannot cause harm. Severity is low because the information is non-sensitive and universally available.

From the tool's definition Tool name and description indicate a simple retrieval operation: 'Get current time in specified timezone.' No modification, execution of arbitrary code, deletion, or financial effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

current_time Allowed

current_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": {
    "current_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 current_time call is checked against it from then on.

FAQ

Questions about current_time

What does the current_time tool do? +

Get current time in specified timezone. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.

What parameters does current_time accept? +

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

How do I enforce a policy on current_time? +

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

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

Can I rate-limit current_time? +

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

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

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