Return current real time (system clock). Use this to avoid AI clock drift. Returns ISO timestamp, epoch, and timezone.
AI agents call get_now to retrieve information from Claude Sync without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that retrieves system clock information. It has no ability to modify, delete, or execute anything. The blast radius of misuse is minimal—an agent receiving incorrect time data might make poor scheduling decisions, but cannot cause damage. Severity is low because time data is non-sensitive and read-only access is benign.
From the tool's definition Tool returns current time data (ISO timestamp, epoch, timezone) with no side effects. Description explicitly states it 'Return[s] current real time' for informational purposes ('to avoid AI clock drift').
Attacks that exploit this kind of access
Return current real time (system clock). Use this to avoid AI clock drift. Returns ISO timestamp, epoch, and timezone. It is categorised as a Read tool in the Claude Sync MCP Server, which means it retrieves data without modifying state.
Register the Claude Sync MCP server in PolicyLayer and add a rule for get_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 Claude Sync. Nothing to install.
get_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 get_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 get_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.
get_now is provided by the Claude Sync MCP server (the-firmament/claude-sync). 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 →