Convert time between two locations via GET /v3/timezone/convert. Works on free and paid plans. Cost: 1 credit. Specify source and destination by IANA timezone, coordinates, location, airport code, or UN/LOCODE. Returns original time, converted time, diff_hour, and diff_min.
Risk signalsHigh parameter count (15 properties)
Part of the Ipgeolocation Io server.
Free to start. No card required.
AI agents use convert_timezone to create or modify resources in Ipgeolocation Io. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call convert_timezone repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ipgeolocation Io.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"convert_timezone": {
"limits": [
{
"counter": "convert_timezone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Ipgeolocation Io policy for all 16 tools.
These attack patterns abuse exactly the kind of access convert_timezone gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Convert time between two locations via GET /v3/timezone/convert. Works on free and paid plans. Cost: 1 credit. Specify source and destination by IANA timezone, coordinates, location, airport code, or UN/LOCODE. Returns original time, converted time, diff_hour, and diff_min.. It is categorised as a Write tool in the Ipgeolocation Io MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ipgeolocation Io MCP server in PolicyLayer and add a rule for convert_timezone: 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 Ipgeolocation Io. Nothing to install.
convert_timezone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convert_timezone 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 convert_timezone. 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.
convert_timezone is provided by the Ipgeolocation Io MCP server (ipgeolocation-io-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Ipgeolocation Io tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.