resolve_datetime · Temporal Cortex Calendar MCP

WHAT IT DOES

What resolve_datetime does on Temporal Cortex Calendar MCP

AI agents use resolve_datetime to create or update resources in Temporal Cortex Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Temporal Cortex Calendar MCP environment.

PARAMETERS

Parameter	Type	Required	Description
`timezone`	string \| null	—	IANA timezone. Omit to use configured timezone.
`expression`	string	Yes	Time expression (e.g., "next Tuesday at 2pm", "tomorrow", "+3h", or RFC 3339).

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why resolve_datetime needs a policy

An AI agent can call resolve_datetime faster than any human can review — one bad instruction and it creates or modifies resources in Temporal Cortex Calendar MCP by the hundred, each call as confident as the last.

Risk signalsAccepts freeform code/query input (expression)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_datetime Rate-limited

resolve_datetime stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_datetime": {
      "limits": [
        {
          "counter": "resolve_datetime_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Temporal Cortex Calendar MCP, so you can run agents against it safely.

FAQ

Questions about resolve_datetime

What does the resolve_datetime tool do? +

Resolve a human-readable time expression to an absolute datetime. Supports: 'next Tuesday at 2pm', 'tomorrow morning', '+3h', 'in 2 hours', 'start of next week', RFC 3339 passthrough, and more. It is categorised as a Write tool in the Temporal Cortex Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does resolve_datetime accept? +

resolve_datetime accepts 2 parameters: timezone, expression. Required: expression. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_datetime? +

Register the Temporal Cortex Calendar MCP server in PolicyLayer and add a rule for resolve_datetime: 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.

What risk level is resolve_datetime? +

resolve_datetime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_datetime? +

Yes. Add a rate_limit block to the resolve_datetime 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.

How do I block resolve_datetime completely? +

Set action: deny in the PolicyLayer policy for resolve_datetime. 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.

What MCP server provides resolve_datetime? +

resolve_datetime 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.