Build and transform spatial weights in one step. Parameters: - data_path: Path to point shapefile or GeoPackage - method: 'queen', 'rook', 'distance_band', or 'knn' - id_field: Optional field name for IDs - threshold: Distance threshold (required if method='distance_band') - k: Number of neighbor...
AI agents invoke build_and_transform_weights to trigger actions in GIS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a multi-step geospatial computation (building spatial weights and transforming them) against input files. It does not merely read data passively nor does it destructively delete or modify source data. It performs a computational operation whose output depends on method, threshold, and transform parameters — fitting the Execute category.
From the tool's definition Build and transform spatial weights in one step — performs spatial analysis operations (constructing spatial weight matrices and applying transformations) on geospatial data files
Documented attack patterns abuse exactly the kind of access build_and_transform_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 build_and_transform_weights:
{
"version": "1",
"default": "deny",
"tools": {
"build_and_transform_weights": {
"limits": [
{
"counter": "build_and_transform_weights_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}build_and_transform_weights stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Build and transform spatial weights in one step. Parameters: - data_path: Path to point shapefile or GeoPackage - method: 'queen', 'rook', 'distance_band', or 'knn' - id_field: Optional field name for IDs - threshold: Distance threshold (required if method='distance_band') - k: Number of neighbors (required if method='knn') - binary: True for binary weights, False for inverse distance (DistanceBand only) - transform_type: 'r', 'v', 'b', 'o', or 'd'. It is categorised as a Execute tool in the GIS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for build_and_transform_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.
build_and_transform_weights is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_and_transform_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 build_and_transform_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.
build_and_transform_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.