Calculates the duration between two timestamps
AI agents call calculate_difference to retrieve information from Temporal Awareness MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a mathematical calculation on temporal data (computing the difference between two timestamps) and returns a result. It does not create, modify, delete, execute code, trigger operations, or move money. It is a read-only operation that retrieves or derives information from provided inputs.
From the tool's definition Tool name is 'calculate_difference' and description states it 'Calculates the duration between two timestamps' - a pure calculation operation that retrieves or computes data without side effects.
Attacks that exploit this kind of access
Calculates the duration between two timestamps. It is categorised as a Read tool in the Temporal Awareness MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Temporal Awareness MCP Server MCP server in PolicyLayer and add a rule for calculate_difference: 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 Awareness MCP Server. Nothing to install.
calculate_difference 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 calculate_difference 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 calculate_difference. 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.
calculate_difference is provided by the Temporal Awareness MCP Server MCP server (pmbstyle/temporal-awareness-mcp). 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 →