pg_cron_list_jobs
List all scheduled cron jobs. Shows job ID, name, schedule, command, and status. Jobs without names (jobname: null) must be referenced by jobId. Default limit: 50 rows.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-cron-list-jobs.md
What pg_cron_list_jobs does on PostgreSQL MCP Server
AI agents call pg_cron_list_jobs to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pg_cron_list_jobs is rated Low
This is a read-only operation that queries and displays existing cron job metadata. It has no side effects, does not execute jobs, and does not modify any data. The blast radius of misuse is minimal—an attacker gains visibility into scheduled tasks but cannot trigger or alter them.
From the tool's definition Tool name contains 'list', description states 'List all scheduled cron jobs' and 'Shows job ID, name, schedule, command, and status' — retrieves and displays information without modifying or executing any jobs.
Attacks that exploit this kind of access
The rule that runs pg_cron_list_jobs 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_list_jobs, this is the rule to start with:
pg_cron_list_jobs is read-only, so it stays allowed. 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_list_jobs call is checked against it from then on.
Questions about pg_cron_list_jobs
List all scheduled cron jobs. Shows job ID, name, schedule, command, and status. Jobs without names (jobname: null) must be referenced by jobId. Default limit: 50 rows. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_cron_list_jobs: 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_list_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pg_cron_list_jobs 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_list_jobs. 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_list_jobs 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.
This server
Across the catalogue