Compute focal (moving window) statistics on a raster. Args: raster_path: Path to the input raster. statistic: Statistic to compute ('mean', 'min', 'max', 'std'). size: Window size (odd integer). output_path: Optional path to save the result. Returns: Dictionary with status, message, and output pa...
AI agents invoke focal_statistics 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 runs a computational operation (moving window statistics) on raster data and can write results to a file. The primary action is executing a geospatial computation, not merely reading data. When an output_path is provided, it also writes new data to disk. Execute is more appropriate than Write because the tool runs an algorithm/transformation rather than simply storing data.
From the tool's definition 'Compute focal (moving window) statistics on a raster' and 'Optional path to save the result' — performs computational processing on raster data and optionally writes output to disk
Documented attack patterns abuse exactly the kind of access focal_statistics 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 focal_statistics:
{
"version": "1",
"default": "deny",
"tools": {
"focal_statistics": {
"limits": [
{
"counter": "focal_statistics_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}focal_statistics 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.
Compute focal (moving window) statistics on a raster. Args: raster_path: Path to the input raster. statistic: Statistic to compute ('mean', 'min', 'max', 'std'). size: Window size (odd integer). output_path: Optional path to save the result. Returns: Dictionary with status, message, and output path if saved. 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 focal_statistics: 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.
focal_statistics 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 focal_statistics 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 focal_statistics. 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.
focal_statistics 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.