Adaptive DBSCAN clustering (requires coordinates, no dependent_var).
AI agents invoke adbscan 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 computational algorithm (Adaptive DBSCAN clustering) against spatial coordinate data. It does not merely read stored data nor does it persist results, but rather performs active computation/analysis. No destructive, financial, or write-side-effects are indicated, placing it in Execute.
From the tool's definition 'Adaptive DBSCAN clustering (requires coordinates, no dependent_var)' — runs a clustering algorithm on input coordinate data
Documented attack patterns abuse exactly the kind of access adbscan 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 adbscan:
{
"version": "1",
"default": "deny",
"tools": {
"adbscan": {
"limits": [
{
"counter": "adbscan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}adbscan 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.
Adaptive DBSCAN clustering (requires coordinates, no dependent_var). 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 adbscan: 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.
adbscan 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 adbscan 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 adbscan. 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.
adbscan 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.