join_counts_local

THE RISK

Low Risk

Why join_counts_local needs a policy

Join counts is a standard GIS/spatial statistics metric used to measure spatial autocorrelation and clustering. The operation retrieves or computes statistics from spatial data without modifying, deleting, or executing external operations. It aligns with the Read category as a query/calculation tool.

From the tool's definition Tool name 'join_counts_local' and description 'Local Join Counts' indicate a spatial statistical calculation that computes local join count statistics, which is a read-only geospatial analysis operation (similar to sibling tools like calculate_geodetic_area…

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

POLICY

How to control join_counts_local

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "join_counts_local": {}
  }
}

join_counts_local is read-only, so it stays allowed — but 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.

CAP 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 ols_with_spatial_diagnostics_safe Safe MCP pipeline: Read shapefile, build/load W, convert numeric, check NaNs, run OLS. 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.

All 98 GIS MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about join_counts_local

What does the join_counts_local tool do? +

Local Join Counts. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on join_counts_local? +

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

join_counts_local is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit join_counts_local? +

Yes. Add a rate_limit block to the join_counts_local 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 join_counts_local completely? +

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

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

Enforce policy on every GIS MCP Server tool call.

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.

CHECK YOUR STACK →