unclick_timestamp_convert
Convert a timestamp (ISO, Unix seconds, or Unix ms) to all common formats.
This record as markdown: /tools/creativelead-unclick/unclick-timestamp-convert.md
What unclick_timestamp_convert does on UnClick
AI agents call unclick_timestamp_convert as a supporting operation in UnClick workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
timestamp | object | — | ISO string, Unix seconds (e.g. 1700000000), or Unix ms (e.g. 1700000000000) |
Parameters from the server's own tool schema.
Why unclick_timestamp_convert is rated Low
This tool purely performs a local data transformation/conversion with no side effects, no data retrieval, no writes, no execution, and no financial operations. It simply converts a timestamp between formats.
From the tool's definition Convert a timestamp (ISO, Unix seconds, or Unix ms) to all common formats.
Attacks that exploit this kind of access
The rule that runs unclick_timestamp_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 unclick_timestamp_convert, this is the rule to start with:
unclick_timestamp_convert gets a rate cap, and 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 unclick_timestamp_convert call is checked against it from then on.
Questions about unclick_timestamp_convert
Convert a timestamp (ISO, Unix seconds, or Unix ms) to all common formats. It is categorised as a Other tool in the UnClick MCP Server, which means it performs auxiliary operations.
unclick_timestamp_convert accepts 1 parameter: 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 unclick_timestamp_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.
unclick_timestamp_convert is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unclick_timestamp_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 unclick_timestamp_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.
unclick_timestamp_convert is provided by the UnClick MCP server (creativelead/unclick). 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