pg_cron_job_run_details

View execution history for cron jobs. Shows start/end times, status, and return messages. Useful for monitoring and debugging scheduled jobs. Default limit is 10 rows.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-cron-job-run-details.md

What pg_cron_job_run_details does on PostgreSQL MCP Server

AI agents call pg_cron_job_run_details 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_job_run_details is rated Low

This tool only retrieves and displays historical execution data for cron jobs. It performs no modifications, executions, or deletions — purely a read/query operation for monitoring purposes.

From the tool's definition View execution history for cron jobs. Shows start/end times, status, and return messages. Useful for monitoring and debugging scheduled jobs.

Questions about pg_cron_job_run_details

What does the pg_cron_job_run_details tool do? +

View execution history for cron jobs. Shows start/end times, status, and return messages. Useful for monitoring and debugging scheduled jobs. Default limit is 10 rows. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_cron_job_run_details? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_cron_job_run_details: 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.

What risk level is pg_cron_job_run_details? +

pg_cron_job_run_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pg_cron_job_run_details? +

Yes. Add a rate_limit block to the pg_cron_job_run_details 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.

How do I block pg_cron_job_run_details completely? +

Set action: deny in the PolicyLayer policy for pg_cron_job_run_details. 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.

What MCP server provides pg_cron_job_run_details? +

pg_cron_job_run_details 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.