Determine the area reachable within a specified time or driving distance
AI agents call tomtom-reachable-range to retrieve information from TomTom MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries TomTom's routing/geolocation services to calculate and return reachable areas based on time or distance parameters. It performs a read-only lookup operation similar to other sibling tools (search, geocode, routing queries). There are no side effects, data modifications, destructive actions, financial transactions, or code execution involved.
From the tool's definition Tool name 'tomtom-reachable-range' and description 'Determine the area reachable within a specified time or driving distance' indicate a query operation that retrieves geolocation data without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access tomtom-reachable-range gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TomTom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tomtom-reachable-range:
{
"version": "1",
"default": "deny",
"tools": {
"tomtom-reachable-range": {}
}
}tomtom-reachable-range is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Determine the area reachable within a specified time or driving distance. It is categorised as a Read tool in the TomTom MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TomTom MCP Server MCP server in PolicyLayer and add a rule for tomtom-reachable-range: 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 TomTom MCP Server. Nothing to install.
tomtom-reachable-range 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 tomtom-reachable-range 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 tomtom-reachable-range. 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.
tomtom-reachable-range is provided by the TomTom MCP Server MCP server (tomtom-international/tomtom-maps-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 TomTom MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 TomTom MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.