pg_bounding_box

Find geometries within a bounding box. Swapped min/max values are auto-corrected. Default limit: 10 rows.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-bounding-box.md

WHAT IT DOES

What pg_bounding_box does on PostgreSQL MCP Server

AI agents call pg_bounding_box 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.

RISK

Why pg_bounding_box is rated Low

This tool retrieves/queries spatial data (geometries) filtered by bounding box coordinates. It performs a read-only search operation with built-in safety limits. No data is created, modified, deleted, or executed; it is purely a retrieval function. The auto-correction of swapped min/max values is a safety feature that does not elevate the risk category.

From the tool's definition Tool name and description indicate it 'Find[s] geometries within a bounding box' with a 'Default limit: 10 rows' — a spatial query operation with no modification or deletion capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_bounding_box 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_bounding_box, this is the rule to start with:

pg_bounding_box Allowed

pg_bounding_box is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pg_bounding_box": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_bounding_box call is checked against it from then on.

FAQ

Questions about pg_bounding_box

What does the pg_bounding_box tool do? +

Find geometries within a bounding box. Swapped min/max values are auto-corrected. 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.

How do I enforce a policy on pg_bounding_box? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_bounding_box: 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.

What risk level is pg_bounding_box? +

pg_bounding_box is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pg_bounding_box? +

Yes. Add a rate_limit block to the pg_bounding_box 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.

How do I block pg_bounding_box completely? +

Set action: deny in the PolicyLayer policy for pg_bounding_box. 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.

What MCP server provides pg_bounding_box? +

pg_bounding_box 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.

KEEP EXPLORING

What pg_bounding_box does on PostgreSQL MCP Server

Why pg_bounding_box is rated Low

The rule that runs pg_bounding_box safely

Questions about pg_bounding_box

More on PostgreSQL MCP Server, and thousands of servers like it.