pg_point_in_polygon
Check if a point is within any polygon in a table. The geometry column should contain POLYGON or MULTIPOLYGON geometries. Default limit: 10 rows.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-point-in-polygon.md
What pg_point_in_polygon does on PostgreSQL MCP Server
AI agents call pg_point_in_polygon 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_point_in_polygon is rated Low
This is a spatial query operation that retrieves data based on geometric intersection logic. It has no side effects—it only checks a condition and returns matching rows. This is clearly a Read operation with minimal risk.
From the tool's definition Tool performs a geometric query ('Check if a point is within any polygon') to retrieve matching data. Returns results with a default limit of 10 rows. No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs pg_point_in_polygon 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_point_in_polygon, this is the rule to start with:
pg_point_in_polygon 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_point_in_polygon call is checked against it from then on.
Questions about pg_point_in_polygon
Check if a point is within any polygon in a table. The geometry column should contain POLYGON or MULTIPOLYGON geometries. Default limit: 10 rows. 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_point_in_polygon: 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_point_in_polygon 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_point_in_polygon 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_point_in_polygon. 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_point_in_polygon 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