Get the distance and time between two points
AI agents call get_distance_and_time to retrieve information from MCP Calendar Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calculated distance and duration metrics between geographic coordinates. It performs no side effects—it does not create, modify, delete, or execute arbitrary operations. It is purely informational, returning read-only data. The context of calendar management shows it supports travel time calculations between meetings, which is consistent with a data retrieval operation.
From the tool's definition Tool name 'get_distance_and_time' and description 'Get the distance and time between two points' indicate a query operation that retrieves distance and travel time data without modifying any state.
Attacks that exploit this kind of access
Get the distance and time between two points. It is categorised as a Read tool in the MCP Calendar Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Calendar Server MCP server in PolicyLayer and add a rule for get_distance_and_time: 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 MCP Calendar Server. Nothing to install.
get_distance_and_time 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 get_distance_and_time 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 get_distance_and_time. 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.
get_distance_and_time is provided by the MCP Calendar Server MCP server (tekuor/mcp-calendar). 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 →