AI agents call download_boundaries to retrieve information from GIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or fetch geospatial boundary datasets without creating, modifying, or deleting data. This aligns with the 'Read' category. Confidence is reduced to 0.7 due to the empty description—if the tool unexpectedly cached, transformed, or persisted data as a side effect, the classification could shift, but based on naming convention and server purpose, read-only data retrieval is most likely.
From the tool's definition Tool name 'download_boundaries' suggests retrieving geospatial boundary data. The server context (GIS operations, geometric operations, spatial measurements) indicates this is a data retrieval operation.
Documented attack patterns abuse exactly the kind of access download_boundaries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for download_boundaries:
{
"version": "1",
"default": "deny",
"tools": {
"download_boundaries": {}
}
}download_boundaries 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.
download_boundaries. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for download_boundaries: 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 GIS MCP Server. Nothing to install.
download_boundaries 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 download_boundaries 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 download_boundaries. 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.
download_boundaries is provided by the GIS MCP Server MCP server (mahdin75/gis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GIS MCP Server, 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.
98 GIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.