Low Risk

tomtom-nearby

Discover services within a radius

How to control tomtom-nearby ↓

AI agents call tomtom-nearby 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.

Low Risk

This tool queries TomTom's location services to find nearby points of interest or services within a specified geographic radius. It has no side effects, does not modify data, execute code, delete records, or move money. It is a straightforward read operation similar to other sibling tools (tomtom-fuzzy-search, tomtom-poi-search, tomtom-reverse-geocode) that retrieve geolocation information.

From the tool's definition Tool name 'tomtom-nearby' and description 'Discover services within a radius' indicate a search/query operation that retrieves location data without modifying or deleting anything.

Documented attack patterns abuse exactly the kind of access tomtom-nearby 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-nearby:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tomtom-nearby": {}
  }
}

tomtom-nearby is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register TomTom MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the tomtom-nearby tool do? +

Discover services within a radius. It is categorised as a Read tool in the TomTom MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tomtom-nearby? +

Register the TomTom MCP Server MCP server in PolicyLayer and add a rule for tomtom-nearby: 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.

What risk level is tomtom-nearby? +

tomtom-nearby is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tomtom-nearby? +

Yes. Add a rate_limit block to the tomtom-nearby 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.

How do I block tomtom-nearby completely? +

Set action: deny in the PolicyLayer policy for tomtom-nearby. 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.

What MCP server provides tomtom-nearby? +

tomtom-nearby 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.

Enforce policy on every TomTom MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.