pg_detach_partition
Detach a partition. Use concurrently: true for non-blocking. Use finalize: true only after an interrupted CONCURRENTLY detach.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-detach-partition.md
What pg_detach_partition does on PostgreSQL MCP Server
AI agents call pg_detach_partition 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_detach_partition is rated Critical
Detaching a partition is a DDL operation that structurally modifies the database schema. Although the partition data is not deleted, the detachment is effectively irreversible without explicit re-attachment steps, can break queries and application logic relying on the partitioned structure, and operates at a high blast radius affecting potentially large datasets and dependent queries.
From the tool's definition 'Detach a partition' — removing a partition from a partitioned table is a structural DDL change that alters the table layout.
Attacks that exploit this kind of access
The rule that runs pg_detach_partition 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_detach_partition, this is the rule to start with:
pg_detach_partition 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_detach_partition call is checked against it from then on.
Questions about pg_detach_partition
Detach a partition. Use concurrently: true for non-blocking. Use finalize: true only after an interrupted CONCURRENTLY detach. 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_detach_partition: 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_detach_partition 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_detach_partition 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_detach_partition. 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_detach_partition 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