Current date, time, and timestamp for any timezone worldwide. Returns UTC and local timestamps, unix epoch, day of week. Useful for scheduling, logging, and time-aware operations. (Paid via x402: $0.001 USDC per call on Base, settled automatically.)
AI agents call navi_timestamp to retrieve information from Navi X402 without modifying anything — 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 (e.g. America/New_York, Europe/Paris, Asia/Singapore, Asia/Tokyo). Defaults to UTC. |
Parameters from the server's own tool schema.
This is a straightforward time/date query function. Although the server enables payments via cryptocurrency, the tool itself performs only a read operation—it retrieves and formats temporal data.
From the tool's definition Tool returns "current date, time, and timestamp for any timezone worldwide" with "UTC and local timestamps, unix epoch, day of week" — purely informational retrieval with no side effects, no data modification, no code execution, no financial transaction…
Attacks that exploit this kind of access
Current date, time, and timestamp for any timezone worldwide. Returns UTC and local timestamps, unix epoch, day of week. Useful for scheduling, logging, and time-aware operations. (Paid via x402: $0.001 USDC per call on Base, settled automatically.). It is categorised as a Read tool in the Navi X402 MCP Server, which means it retrieves data without modifying state.
navi_timestamp accepts 1 parameter: timezone. The full parameter table on this page comes from the server's own tool schema.
Register the Navi X402 MCP server in PolicyLayer and add a rule for navi_timestamp: 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 Navi X402. Nothing to install.
navi_timestamp 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 navi_timestamp 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 navi_timestamp. 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.
navi_timestamp is provided by the Navi X402 MCP server (navi-x402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →