pg_cron_unschedule
Remove a scheduled cron job by its ID or name. If both are provided, jobName takes precedence. Job ID accepts numbers or numeric strings. Works for both active and inactive jobs.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-cron-unschedule.md
What pg_cron_unschedule does on PostgreSQL MCP Server
AI agents call pg_cron_unschedule 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_unschedule is rated Critical
The tool performs an irreversible deletion operation on a system resource (scheduled cron job). Once unscheduled, the job is removed and will not re-execute unless manually recreated. This is a destructive action that cannot be reversed, matching the Destructive category definition. Severity is high because unscheduling critical cron jobs (backups, maintenance tasks, alerts) could have significant operational impact.
From the tool's definition Tool description explicitly states 'Remove a scheduled cron job by its ID or name' — the 'Remove' action irreversibly deletes a cron job. This cannot be undone and the scheduled operations will cease to execute.
Attacks that exploit this kind of access
The rule that runs pg_cron_unschedule 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_unschedule, this is the rule to start with:
pg_cron_unschedule 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_unschedule call is checked against it from then on.
Questions about pg_cron_unschedule
Remove a scheduled cron job by its ID or name. If both are provided, jobName takes precedence. Job ID accepts numbers or numeric strings. Works for both active and inactive jobs. 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_unschedule: 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_unschedule 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_unschedule 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_unschedule. 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_unschedule 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