Calculer un itinéraire entre deux points avec l
AI agents call calculate_route to retrieve information from French Open Data & IGN without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves route information between two geographic points. It performs a read-only query against routing data without creating, modifying, deleting, or executing arbitrary code. The operation is deterministic and repeatable with no side effects. While truncated, the description and tool name indicate geographic data retrieval rather than any form of data mutation or external command execution.
From the tool's definition Tool name 'calculate_route' and description indicating it calculates a route between two points. The verb 'calculate' and the context of routing computation suggest data retrieval and computation without modification or side effects.
Documented attack patterns abuse exactly the kind of access calculate_route gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and French Open Data & IGN, and nothing reaches the server without passing your rules. This is the rule we recommend for calculate_route:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_route": {}
}
}calculate_route 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.
Calculer un itinéraire entre deux points avec l. It is categorised as a Read tool in the French Open Data & IGN MCP Server, which means it retrieves data without modifying state.
Register the French Open Data & IGN MCP server in PolicyLayer and add a rule for calculate_route: 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 French Open Data & IGN. Nothing to install.
calculate_route 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 calculate_route 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 calculate_route. 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.
calculate_route is provided by the French Open Data & IGN MCP server (nikoko107/mcp-datagouv-ign). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from French Open Data & IGN, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 French Open Data & IGN tools catalogued and risk-classified — across an index of 43,000+ MCP servers.