Typo-tolerant search for addresses, points of interest, and geographies
AI agents call tomtom-fuzzy-search 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 geolocation database to retrieve matching locations, addresses, or points of interest based on fuzzy search criteria. It has no capability to modify, delete, or execute external operations—it only returns search results. The blast radius of misuse is minimal (e.g., excessive queries or privacy concerns around location searches), but no irreversible actions or financial impact are possible.
From the tool's definition Tool provides 'typo-tolerant search for addresses, points of interest, and geographies' with no mention of data modification, deletion, or external side effects.
Documented attack patterns abuse exactly the kind of access tomtom-fuzzy-search 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-fuzzy-search:
{
"version": "1",
"default": "deny",
"tools": {
"tomtom-fuzzy-search": {}
}
}tomtom-fuzzy-search 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.
Typo-tolerant search for addresses, points of interest, and geographies. 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-fuzzy-search: 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-fuzzy-search 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-fuzzy-search 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-fuzzy-search. 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-fuzzy-search 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.