convert_timezone
Convert timestamps between timezones. Use this when you need to express times in a different timezone. Supports common zones: UTC, EST, PST, CET, IST, JST, AEST, etc. Parameters: timestamp — ISO date string (default: current time). from_tz — Source timezone code (default: 'UTC'). to_tz — Target t...
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/convert-timezone.md
What convert_timezone does on X402 Middleware
AI agents call convert_timezone to retrieve information from X402 Middleware 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 |
|---|---|---|---|
to_tz | string | — | |
from_tz | string | — | |
timestamp | string | — |
Parameters from the server's own tool schema.
Why convert_timezone is rated Low
This tool performs a pure computation/conversion of time data between timezones. It has no side effects, does not modify or store any data, and simply transforms an input timestamp into a different timezone representation. This is a Read/query-style operation with minimal risk.
From the tool's definition Convert timestamps between timezones... express times in a different timezone
Attacks that exploit this kind of access
The rule that runs convert_timezone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_timezone, this is the rule to start with:
convert_timezone 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 X402 Middleware, apply this rule, and every convert_timezone call is checked against it from then on.
Questions about convert_timezone
Convert timestamps between timezones. Use this when you need to express times in a different timezone. Supports common zones: UTC, EST, PST, CET, IST, JST, AEST, etc. Parameters: timestamp — ISO date string (default: current time). from_tz — Source timezone code (default: 'UTC'). to_tz — Target timezone code (default: 'UTC'). It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
convert_timezone accepts 3 parameters: to_tz, from_tz, timestamp. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware 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 X402 Middleware. Nothing to install.
convert_timezone 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 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 X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue