pg_migration_risks
Analyze proposed DDL statements for risks: data loss, lock contention, constraint violations, and breaking changes. Pre-flight check before executing migrations.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-migration-risks.md
What pg_migration_risks does on PostgreSQL MCP Server
AI agents call pg_migration_risks 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_migration_risks is rated Low
This tool performs analysis/inspection of proposed DDL statements without actually executing them. It reads and evaluates risk factors (data loss, lock contention, constraint violations, breaking changes) as a pre-flight check. No data is modified or executed. Severity is medium because misclassification or misleading analysis could lead to unsafe migrations being approved.
From the tool's definition Analyze proposed DDL statements for risks... Pre-flight check before executing migrations
Attacks that exploit this kind of access
The rule that runs pg_migration_risks 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_migration_risks, this is the rule to start with:
pg_migration_risks 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_migration_risks call is checked against it from then on.
Questions about pg_migration_risks
Analyze proposed DDL statements for risks: data loss, lock contention, constraint violations, and breaking changes. Pre-flight check before executing migrations. 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_migration_risks: 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_migration_risks 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_migration_risks 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_migration_risks. 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_migration_risks 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