spatial_intersection
AI agents call spatial_intersection to retrieve information from Données Québec MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Spatial intersection operations in GIS are fundamentally geometric queries that analyze overlaps between spatial features without modifying data. Given the server's focus on querying and analyzing open data, and the lack of mutation language (create, delete, modify), this is classified as Read.
From the tool's definition Tool name 'spatial_intersection' implies a query operation on geospatial data. No description provided, but sibling tools (describe_geospatial_layer, get_geospatial_features, find_and_query) are all Read operations.
Attacks that exploit this kind of access
spatial_intersection. It is categorised as a Read tool in the Données Québec MCP MCP Server, which means it retrieves data without modifying state.
Register the Données Québec MCP server in PolicyLayer and add a rule for spatial_intersection: 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 Données Québec MCP. Nothing to install.
spatial_intersection 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 spatial_intersection 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 spatial_intersection. 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.
spatial_intersection is provided by the Données Québec MCP server (stefen-taime/donneesqc-mcp). 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 →