AI agents call spatial-join to retrieve information from PostGIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Spatial joins are fundamental relational/spatial query operations that retrieve matched records from two tables based on geometric relationships (intersection, containment, proximity, etc.). They do not modify source data, create side effects, or execute arbitrary operations. The operation is limited in scope—joining predefined tables with spatial predicates—making it a safe read operation.
From the tool's definition spatial-join performs a join operation between two tables based on spatial relationships. Despite the term 'join', this is a query operation that retrieves and correlates data without modifying, deleting, or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access spatial-join gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostGIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for spatial-join:
{
"version": "1",
"default": "deny",
"tools": {
"spatial-join": {}
}
}spatial-join 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.
İki tablo arasında mekansal join işlemi yap. It is categorised as a Read tool in the PostGIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostGIS MCP Server MCP server in PolicyLayer and add a rule for spatial-join: 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 PostGIS MCP Server. Nothing to install.
spatial-join 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 spatial-join 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 spatial-join. 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.
spatial-join is provided by the PostGIS MCP Server MCP server (receptopalak/postgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostGIS 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.
25 PostGIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.