// MCP TOOL REFERENCE

ols_with_spatial_diagnostics_safe

ServerGIS MCP Server
CategoryExecute

How to control ols_with_spatial_diagnostics_safe ↓

WHAT IT DOES

What ols_with_spatial_diagnostics_safe does on GIS MCP Server

AI agents invoke ols_with_spatial_diagnostics_safe 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.

THE RISK

High Risk

Why ols_with_spatial_diagnostics_safe needs a policy

This tool executes statistical computations (OLS regression analysis) triggered by user parameters. Although it is read-only with respect to the input shapefile (does not modify the original), the core action is executing an analysis operation with side effects (generating outputs, potentially consuming compute resources).

From the tool's definition Tool performs 'run OLS' (Ordinary Least Squares regression) which executes statistical analysis operations on user-supplied data and parameters.

Documented attack patterns abuse exactly the kind of access ols_with_spatial_diagnostics_safe gives an agent:

POLICY

How to control ols_with_spatial_diagnostics_safe

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 ols_with_spatial_diagnostics_safe:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ols_with_spatial_diagnostics_safe": {
      "limits": [
        {
          "counter": "ols_with_spatial_diagnostics_safe_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

ols_with_spatial_diagnostics_safe 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.

Create a free account and register GIS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GIS MCP Server tools

Execute build_and_transform_weights Build and transform spatial weights in one step. Parameters: - data_path: Path to Execute transform_coordinates Transform coordinates between CRS. Execute adbscan Adaptive DBSCAN clustering (requires coordinates, no dependent_var). Execute raster_algebra raster_algebra Execute snap_geometry Snap one geometry to another using shapely.ops.snap. Args: geometry1: WKT stri Execute focal_statistics Compute focal (moving window) statistics on a raster. Args: raster_path: Path Write build_transform_and_save_weights Pipeline: Read shapefile, build spatial weights, optionally transform, and save to file. Write scale_geometry Scale a geometry.

All 98 GIS MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in GIS MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ols_with_spatial_diagnostics_safe

What does the ols_with_spatial_diagnostics_safe tool do? +

Safe MCP pipeline: Read shapefile, build/load W, convert numeric, check NaNs, run OLS. Parameters: - data_path: path to shapefile or GeoPackage - y_field: dependent variable column name - x_fields: list of independent variable column names - weights_path: optional path to existing weights file (.gal or .gwt) - weights_method: 'queen', 'rook', 'distance_band', or 'knn' (used if weights_path not provided) - id_field: optional attribute name to use as observation IDs - threshold: required if method='distance_band' - k: required if method='knn' - binary: True for binary weights (DistanceBand only). 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.

How do I enforce a policy on ols_with_spatial_diagnostics_safe? +

Register the GIS MCP Server MCP server in PolicyLayer and add a rule for ols_with_spatial_diagnostics_safe: 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.

What risk level is ols_with_spatial_diagnostics_safe? +

ols_with_spatial_diagnostics_safe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ols_with_spatial_diagnostics_safe? +

Yes. Add a rate_limit block to the ols_with_spatial_diagnostics_safe 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.

How do I block ols_with_spatial_diagnostics_safe completely? +

Set action: deny in the PolicyLayer policy for ols_with_spatial_diagnostics_safe. 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.

What MCP server provides ols_with_spatial_diagnostics_safe? +

ols_with_spatial_diagnostics_safe 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.