Render a custom map image with markers, drawn lines, polygons, and area overlays using server-side rendering.
AI agents call tomtom-dynamic-map 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 generates a map visualization for display purposes. It retrieves and renders map data with user-specified visual overlays, but does not modify, delete, or execute arbitrary operations. No side effects persist beyond the generated image output. Classification as Read is appropriate for data retrieval tools, even when they involve rendering or formatting.
From the tool's definition Tool renders and returns a map image with visual elements (markers, lines, polygons, overlays) without modifying any underlying data. Described as 'Render a custom map image' — a read-only retrieval of rendered visualization.
Documented attack patterns abuse exactly the kind of access tomtom-dynamic-map 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-dynamic-map:
{
"version": "1",
"default": "deny",
"tools": {
"tomtom-dynamic-map": {}
}
}tomtom-dynamic-map 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.
Render a custom map image with markers, drawn lines, polygons, and area overlays using server-side rendering. 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-dynamic-map: 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-dynamic-map 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-dynamic-map 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-dynamic-map. 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-dynamic-map 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.