epoch_now
Get the current Unix epoch timestamp in seconds and milliseconds.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/epoch-now.md
What epoch_now does on UnClick
AI agents call epoch_now 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.
Why epoch_now is rated Low
This tool merely queries and returns the current Unix epoch timestamp. It performs no writes, deletions, code execution, or financial operations. It is a simple, information-retrieval operation with no capability to modify system state or data.
From the tool's definition Tool name 'epoch_now' and description 'Get the current Unix epoch timestamp in seconds and milliseconds' indicate a pure read operation that retrieves the current system time without any side effects or modifications.
Attacks that exploit this kind of access
The rule that runs epoch_now 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_now, this is the rule to start with:
epoch_now 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_now call is checked against it from then on.
Questions about epoch_now
Get the current Unix epoch timestamp in seconds and milliseconds. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for epoch_now: 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_now 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_now 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_now. 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_now 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