pg_cron_schedule_in_database
Schedule a cron job to run in a different database. Useful for cross-database maintenance tasks. Returns the job ID.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-cron-schedule-in-database.md
What pg_cron_schedule_in_database does on PostgreSQL MCP Server
AI agents invoke pg_cron_schedule_in_database to trigger actions in PostgreSQL MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why pg_cron_schedule_in_database is rated High
This tool schedules recurring job execution in a PostgreSQL database via pg_cron. It triggers external/automated operations (cron jobs) that run arbitrary SQL or commands on a schedule, potentially across multiple databases. The blast radius is high because a misused schedule could repeatedly execute destructive or harmful operations across databases, and scheduled jobs persist until explicitly removed.
From the tool's definition 'Schedule a cron job to run in a different database' and 'cross-database maintenance tasks'
Attacks that exploit this kind of access
The rule that runs pg_cron_schedule_in_database 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_schedule_in_database, this is the rule to start with:
pg_cron_schedule_in_database stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_cron_schedule_in_database call is checked against it from then on.
Questions about pg_cron_schedule_in_database
Schedule a cron job to run in a different database. Useful for cross-database maintenance tasks. Returns the job ID. It is categorised as a Execute tool in the PostgreSQL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_cron_schedule_in_database: 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_schedule_in_database is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pg_cron_schedule_in_database 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_schedule_in_database. 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_schedule_in_database 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