time_api_timezones
List all available IANA timezone names from timeapi.io.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/time-api-timezones.md
What time_api_timezones does on UnClick
AI agents call time_api_timezones 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.
Why time_api_timezones is rated Low
This tool queries and returns a static list of timezone names from an external API. It performs a read-only operation with no capability to modify, execute, delete, or affect financial systems. The blast radius of misuse is minimal—an agent could only retrieve timezone information, which is non-sensitive and publicly available data.
From the tool's definition Tool description states 'List all available IANA timezone names' — a retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
The rule that runs time_api_timezones 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_timezones, this is the rule to start with:
time_api_timezones 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_timezones call is checked against it from then on.
Questions about time_api_timezones
List all available IANA timezone names from timeapi.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for time_api_timezones: 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_timezones 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_timezones 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_timezones. 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_timezones 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