Adjust a timestamp by adding or subtracting a duration. DST-aware: '+1d' preserves wall-clock time across daylight saving transitions.
AI agents call adjust_timestamp to retrieve information from Temporal Cortex Calendar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
datetime | string | Yes | RFC 3339 datetime to adjust. |
timezone | string | null | — | IANA timezone for day-level adjustments. Omit to use configured timezone. |
adjustment | string | Yes | Duration adjustment (e.g., "+2h", "-30m", "+1d2h"). |
Parameters from the server's own tool schema.
Even though adjust_timestamp only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Adjust a timestamp by adding or subtracting a duration. DST-aware: '+1d' preserves wall-clock time across daylight saving transitions. It is categorised as a Read tool in the Temporal Cortex Calendar MCP MCP Server, which means it retrieves data without modifying state.
adjust_timestamp accepts 3 parameters: datetime, timezone, adjustment. Required: datetime, adjustment. The full parameter table on this page comes from the server's own tool schema.
Register the Temporal Cortex Calendar MCP server in PolicyLayer and add a rule for adjust_timestamp: 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 Temporal Cortex Calendar MCP. Nothing to install.
adjust_timestamp 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 adjust_timestamp 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 adjust_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.
adjust_timestamp is provided by the Temporal Cortex Calendar MCP server (temporal-cortex/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.