Get commune (municipality) boundaries from the cadastral database. Args: - geom (string, optional): GeoJSON geometry to intersect - code_insee (string, optional): INSEE commune code - code_dep (string, optional): Department code - _limit (number): Max results (default 500) - _start (number): Pagi...
AI agents call ign_get_cadastre_communes to retrieve information from IGN API Carto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward geographic data query tool. It accepts optional geographic or administrative parameters and returns structured boundary data. No side effects, mutations, or irreversible operations are possible. The worst misuse would be unauthorized access to public geographic information, which poses minimal risk.
From the tool's definition Tool retrieves commune boundaries from cadastral database via optional filters (code_insee, code_dep, geom) with pagination parameters (_limit, _start). Returns read-only GeoJSON FeatureCollection. Verbs: 'Get', 'returns'.
Attacks that exploit this kind of access
Get commune (municipality) boundaries from the cadastral database. Args: - geom (string, optional): GeoJSON geometry to intersect - code_insee (string, optional): INSEE commune code - code_dep (string, optional): Department code - _limit (number): Max results (default 500) - _start (number): Pagination offset Returns: GeoJSON FeatureCollection with commune boundaries. It is categorised as a Read tool in the IGN API Carto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IGN API Carto MCP Server MCP server in PolicyLayer and add a rule for ign_get_cadastre_communes: 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 IGN API Carto MCP Server. Nothing to install.
ign_get_cadastre_communes 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 ign_get_cadastre_communes 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 ign_get_cadastre_communes. 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.
ign_get_cadastre_communes is provided by the IGN API Carto MCP Server MCP server (julienkalamon/ign-apicarto-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →