Convert a timestamp between formats: unix epoch (seconds/ms) ↔ ISO 8601 ↔ human-readable ↔ relative ("3 hours ago"). Auto-detects input format. Returns all formats at once plus UTC offset info.
Part of the Timestamp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use convert_timestamp to create or modify resources in Timestamp. 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_timestamp repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Timestamp.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
convert_timestamp:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Timestamp policy for all 5 tools.
Agents calling write-class tools like convert_timestamp have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Convert a timestamp between formats: unix epoch (seconds/ms) ↔ ISO 8601 ↔ human-readable ↔ relative ("3 hours ago"). Auto-detects input format. Returns all formats at once plus UTC offset info.. It is categorised as a Write tool in the Timestamp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for convert_timestamp. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Timestamp MCP server.
convert_timestamp 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_timestamp rule in your Intercept 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 Intercept policy for convert_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.
convert_timestamp is provided by the Timestamp MCP server (openclaw-ai/timestamp-converter). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept