epoch_convert
Convert a Unix epoch timestamp to ISO 8601 and human-readable formats.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/epoch-convert.md
What epoch_convert does on UnClick
AI agents call epoch_convert 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 |
|---|---|---|---|
timestamp | number | Yes | Unix epoch (seconds or milliseconds). |
Parameters from the server's own tool schema.
Why epoch_convert is rated Low
This tool performs a pure data conversion/transformation operation with no side effects. It takes an epoch timestamp as input and returns formatted date strings. No data is written, executed, or deleted.
From the tool's definition Convert a Unix epoch timestamp to ISO 8601 and human-readable formats
Attacks that exploit this kind of access
The rule that runs epoch_convert 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 epoch_convert, this is the rule to start with:
epoch_convert 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 epoch_convert call is checked against it from then on.
Questions about epoch_convert
Convert a Unix epoch timestamp to ISO 8601 and human-readable formats. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
epoch_convert accepts 1 parameter: timestamp. Required: timestamp. 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 epoch_convert: 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.
epoch_convert 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 epoch_convert 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 epoch_convert. 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.
epoch_convert 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