pg_cron_cleanup_history
Delete old job run history records. Helps prevent the cron.job_run_details table from growing too large. By default, removes records older than 7 days.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-cron-cleanup-history.md
What pg_cron_cleanup_history does on PostgreSQL MCP Server
AI agents call pg_cron_cleanup_history 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_cron_cleanup_history is rated Critical
This tool performs irreversible deletion of historical records. Although the deletion targets old data by default (7 days), the operation cannot be undone and permanently removes audit/monitoring information. The high severity reflects that loss of historical job execution data could impair forensic analysis, compliance auditing, and troubleshooting of cron job issues.
From the tool's definition Tool description explicitly states 'Delete old job run history records' and 'removes records older than 7 days', indicating irreversible deletion of data from the cron.job_run_details table.
Attacks that exploit this kind of access
The rule that runs pg_cron_cleanup_history 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_cron_cleanup_history, this is the rule to start with:
pg_cron_cleanup_history 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_cron_cleanup_history call is checked against it from then on.
Questions about pg_cron_cleanup_history
Delete old job run history records. Helps prevent the cron.job_run_details table from growing too large. By default, removes records older than 7 days. 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_cron_cleanup_history: 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_cron_cleanup_history 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_cron_cleanup_history 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_cron_cleanup_history. 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_cron_cleanup_history 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