compute_duration

Compute the duration between two timestamps. Returns days, hours, minutes, seconds, and a human-readable string.

Server Temporal Cortex Calendar MCP temporal-cortex/mcp
Category Read
Risk class Low
Parameters 22 required

What compute_duration does on Temporal Cortex Calendar MCP

AI agents call compute_duration 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.

ParameterTypeRequiredDescription
end string Yes Second timestamp (RFC 3339).
start string Yes First timestamp (RFC 3339).

Parameters from the server's own tool schema.

Why compute_duration needs a policy

Even though compute_duration 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.

Questions about compute_duration

What does the compute_duration tool do? +

Compute the duration between two timestamps. Returns days, hours, minutes, seconds, and a human-readable string. It is categorised as a Read tool in the Temporal Cortex Calendar MCP MCP Server, which means it retrieves data without modifying state.

What parameters does compute_duration accept? +

compute_duration accepts 2 parameters: end, start. Required: end, start. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on compute_duration? +

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

compute_duration is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit compute_duration? +

Yes. Add a rate_limit block to the compute_duration 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 compute_duration completely? +

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

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.