AI agents call join_counts to retrieve information from GIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs geospatial analysis and measurement (join count statistics), which are read-only operations that retrieve or derive information from spatial data without creating, modifying, or deleting any underlying data. It follows the pattern of other analytical tools on this GIS server (e.g., calculate_geodetic_distance, calculate_geodetic_area) that produce derived metrics without side effects.
From the tool's definition 'Global Binary Join Counts' - a statistical/analytical operation that calculates join counts between spatial features based on adjacency or spatial relationships.
Documented attack patterns abuse exactly the kind of access join_counts 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 join_counts:
{
"version": "1",
"default": "deny",
"tools": {
"join_counts": {}
}
} join_counts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Global Binary Join Counts. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for join_counts: 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.
join_counts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the join_counts 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 join_counts. 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.
join_counts 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.