Create a distance-based spatial weights (W) object from point data. - data_path: path to point shapefile or GeoPackage - threshold: distance threshold for neighbors (in CRS units, e.g., meters) - binary: True for binary weights, False for inverse distance weights - id_field: optional attribute na...
AI agents use distance_band_weights to create or update resources in GIS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GIS MCP Server environment.
This tool creates a new spatial weights matrix object based on input parameters and source data. While the weights object is a mathematical/analytical construct (not destructive or irreversible), it constitutes creation of new data structures that persist as outputs.
From the tool's definition Tool creates a spatial weights object from input data (distance_band_weights), which is a derived data structure created from source data.
Documented attack patterns abuse exactly the kind of access distance_band_weights 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 distance_band_weights:
{
"version": "1",
"default": "deny",
"tools": {
"distance_band_weights": {
"limits": [
{
"counter": "distance_band_weights_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}distance_band_weights stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a distance-based spatial weights (W) object from point data. - data_path: path to point shapefile or GeoPackage - threshold: distance threshold for neighbors (in CRS units, e.g., meters) - binary: True for binary weights, False for inverse distance weights - id_field: optional attribute name to use as observation IDs. It is categorised as a Write tool in the GIS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for distance_band_weights: 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.
distance_band_weights is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the distance_band_weights 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 distance_band_weights. 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.
distance_band_weights 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.