pg_partman_set_retention
Configure retention policy for a partition set. Partitions older than the retention period will be dropped or detached during maintenance.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-partman-set-retention.md
What pg_partman_set_retention does on PostgreSQL MCP Server
AI agents call pg_partman_set_retention 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_partman_set_retention is rated Critical
This tool configures a policy that causes partitions to be automatically dropped (irreversible deletion) or detached during maintenance runs. Once dropped, partition data is permanently lost. The blast radius is critical because a misconfigured retention period could cause mass deletion of production database partitions containing large volumes of historical data.
From the tool's definition Partitions older than the retention period will be dropped or detached during maintenance
Attacks that exploit this kind of access
The rule that runs pg_partman_set_retention 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_partman_set_retention, this is the rule to start with:
pg_partman_set_retention 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_partman_set_retention call is checked against it from then on.
Questions about pg_partman_set_retention
Configure retention policy for a partition set. Partitions older than the retention period will be dropped or detached during maintenance. 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_partman_set_retention: 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_partman_set_retention 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_partman_set_retention 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_partman_set_retention. 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_partman_set_retention 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