time_api_current_by_zone
Get the current date and time for an IANA timezone via timeapi.io.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/time-api-current-by-zone.md
What time_api_current_by_zone does on UnClick
AI agents call time_api_current_by_zone to retrieve information from UnClick 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 | string | — | IANA timezone name (default: UTC). E.g. America/New_York. |
Parameters from the server's own tool schema.
Why time_api_current_by_zone is rated Low
This is a straightforward data retrieval operation that queries a time API and returns timezone-specific date/time information. It has no side effects, cannot modify or delete data, and poses minimal risk if misused by an AI agent. The low severity reflects that accurate or inaccurate time data carries negligible impact in isolation.
From the tool's definition Tool name and description indicate retrieval of current date/time data: 'Get the current date and time for an IANA timezone via timeapi.io.' No data modification, deletion, code execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs time_api_current_by_zone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For time_api_current_by_zone, this is the rule to start with:
time_api_current_by_zone is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every time_api_current_by_zone call is checked against it from then on.
Questions about time_api_current_by_zone
Get the current date and time for an IANA timezone via timeapi.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
time_api_current_by_zone accepts 1 parameter: timezone. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for time_api_current_by_zone: 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 UnClick. Nothing to install.
time_api_current_by_zone is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the time_api_current_by_zone 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 time_api_current_by_zone. 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.
time_api_current_by_zone is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue