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.
Risk signalsAccepts freeform code/query input (expression)
Part of the Temporal Cortex MCP server.
Free to start. No card required.
AI agents use resolve_datetime to create or modify resources in Temporal Cortex MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call resolve_datetime repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Temporal Cortex MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"resolve_datetime": {
"limits": [
{
"counter": "resolve_datetime_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Temporal Cortex MCP policy for all 12 tools.
These attack patterns abuse exactly the kind of access resolve_datetime gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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 MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Temporal Cortex 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 MCP. Nothing to install.
resolve_datetime is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
resolve_datetime is provided by the Temporal Cortex MCP server (temporal-cortex/cortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Temporal Cortex MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.