Calculate optimal routes between two locations. Use this tool FIRST when the user asks about directions, routes, travel time, or distance between places (e.g.
AI agents call tomtom-routing 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.
The tool retrieves geolocation routing information and calculations based on input parameters. It has no side effects, does not create or modify data, does not execute arbitrary code or commands, does not delete data, and does not involve financial transactions. This is a straightforward data retrieval operation analogous to 'get' or 'fetch' operations.
From the tool's definition Tool description states 'Calculate optimal routes between two locations' and 'when the user asks about directions, routes, travel time, or distance' — these are queries that retrieve routing data without modifying, deleting, or executing arbitrary operations.
Documented attack patterns abuse exactly the kind of access tomtom-routing 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-routing:
{
"version": "1",
"default": "deny",
"tools": {
"tomtom-routing": {}
}
}tomtom-routing 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.
Calculate optimal routes between two locations. Use this tool FIRST when the user asks about directions, routes, travel time, or distance between places (e.g. 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-routing: 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-routing 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-routing 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-routing. 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-routing 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.