worldtime_by_ip
Get current time based on IP address geolocation.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/worldtime-by-ip.md
What worldtime_by_ip does on UnClick
AI agents call worldtime_by_ip 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 |
|---|---|---|---|
ip | string | — | IP address (omit for your own IP) |
Parameters from the server's own tool schema.
Why worldtime_by_ip is rated Low
This tool performs a read-only lookup operation. It takes an IP address as input, performs geolocation mapping, and returns the corresponding time zone and current time. No data is created, modified, deleted, or irreversibly changed. The blast radius of misuse is minimal—worst case an agent makes unnecessary API calls. This is a classic Read operation that retrieves information without side effects.
From the tool's definition Tool name 'worldtime_by_ip' and description 'Get current time based on IP address geolocation' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs worldtime_by_ip 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 worldtime_by_ip, this is the rule to start with:
worldtime_by_ip 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 worldtime_by_ip call is checked against it from then on.
Questions about worldtime_by_ip
Get current time based on IP address geolocation. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
worldtime_by_ip accepts 1 parameter: ip. 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 worldtime_by_ip: 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.
worldtime_by_ip 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 worldtime_by_ip 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 worldtime_by_ip. 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.
worldtime_by_ip 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