Spatial clustering using distance-based grouping (requires PostGIS)
AI agents invoke geo_cluster to trigger actions in Postgres Mcp Legacy. 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 spatial clustering operation on the database, which involves executing PostGIS geospatial functions and queries. It reads data and performs computational grouping, making it an Execute-level action. It does not appear to modify or delete data, but executing arbitrary spatial queries against the database carries medium risk depending on what parameters are passed and how the query is constructed.
From the tool's definition 'Spatial clustering using distance-based grouping' — executes a spatial computation/query against the database using PostGIS functions
Documented attack patterns abuse exactly the kind of access geo_cluster gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for geo_cluster:
{
"version": "1",
"default": "deny",
"tools": {
"geo_cluster": {
"limits": [
{
"counter": "geo_cluster_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}geo_cluster 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.
Spatial clustering using distance-based grouping (requires PostGIS). It is categorised as a Execute tool in the Postgres Mcp Legacy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for geo_cluster: 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 Postgres Mcp Legacy. Nothing to install.
geo_cluster 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 geo_cluster 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 geo_cluster. 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.
geo_cluster is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres Mcp Legacy, 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.
60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.