pg_geometry_intersection
Compute the intersection of two WKT or GeoJSON geometries. Returns the intersection geometry and whether they intersect.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-geometry-intersection.md
What pg_geometry_intersection does on PostgreSQL MCP Server
AI agents call pg_geometry_intersection to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pg_geometry_intersection is rated Low
This is a pure computational geometry operation that reads two input geometries and returns a derived result. It performs no database modifications, no data deletion, no external operations with side effects, and no financial transactions. It is a mathematical query operation similar to vector math functions, making it a Read category tool with low severity risk.
From the tool's definition Tool computes and returns the intersection of geometries without modifying data: 'Compute the intersection of two WKT or GeoJSON geometries. Returns the intersection geometry and whether they intersect.'
Attacks that exploit this kind of access
The rule that runs pg_geometry_intersection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_geometry_intersection, this is the rule to start with:
pg_geometry_intersection is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_geometry_intersection call is checked against it from then on.
Questions about pg_geometry_intersection
Compute the intersection of two WKT or GeoJSON geometries. Returns the intersection geometry and whether they intersect. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_geometry_intersection: 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 PostgreSQL MCP Server. Nothing to install.
pg_geometry_intersection 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 pg_geometry_intersection 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 pg_geometry_intersection. 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.
pg_geometry_intersection is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue