pg_geo_transform

Transform geometry from one spatial reference system (SRID) to another.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What pg_geo_transform does on PostgreSQL MCP Server

AI agents invoke pg_geo_transform to trigger actions in PostgreSQL MCP Server. 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.

Why pg_geo_transform is rated High

This tool performs a computational transformation operation on geographic/geometric data. While it operates on existing data rather than creating, modifying, or deleting it, it actively executes a PostGIS function with arguments (source and target SRID). The transformation itself is a side-effecting operation that produces computed results.

From the tool's definition Tool name 'pg_geo_transform' and description state it 'Transform[s] geometry from one spatial reference system (SRID) to another' — this executes a PostGIS spatial transformation operation on data.

Questions about pg_geo_transform

What does the pg_geo_transform tool do? +

Transform geometry from one spatial reference system (SRID) to another. It is categorised as a Execute tool in the PostgreSQL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pg_geo_transform? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_geo_transform: 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_geo_transform? +

pg_geo_transform is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pg_geo_transform? +

Yes. Add a rate_limit block to the pg_geo_transform 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_geo_transform completely? +

Set action: deny in the PolicyLayer policy for pg_geo_transform. 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_geo_transform? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.