pg_migration_rollback
Roll back a specific migration by ID or version.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-migration-rollback.md
What pg_migration_rollback does on PostgreSQL MCP Server
AI agents call pg_migration_rollback to permanently remove resources in PostgreSQL MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pg_migration_rollback is rated Critical
Migration rollbacks typically execute destructive DDL operations (DROP TABLE, DROP COLUMN, etc.) that cannot be undone and may permanently destroy data. This is irreversible by nature, making it Destructive with critical severity given the blast radius of schema-level changes on a production database.
From the tool's definition 'Roll back a specific migration' — rolling back a migration reverses schema changes (dropping tables, columns, constraints) in a way that may be irreversible and causes data loss
Attacks that exploit this kind of access
The rule that runs pg_migration_rollback 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_rollback, this is the rule to start with:
pg_migration_rollback is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_migration_rollback call is checked against it from then on.
Questions about pg_migration_rollback
Roll back a specific migration by ID or version. It is categorised as a Destructive tool in the PostgreSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_migration_rollback: 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_rollback is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pg_migration_rollback 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_rollback. 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_rollback 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.
Across the catalogue