This record as markdown: /tools/io-github-devopam-mcpg/list-cron-jobs.md
What list_cron_jobs does on Mcpg
AI agents call list_cron_jobs to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_cron_jobs is rated Low
The tool appears to list or query existing cron jobs in a PostgreSQL database, which is a read-only operation with no side effects. Even though cron jobs control scheduled operations, merely listing them does not execute or modify them. The empty description lowers confidence slightly, but the naming convention strongly suggests a Read operation.
From the tool's definition Tool name 'list_cron_jobs' indicates a listing/querying operation that retrieves cron job information without modifying it. The 'list' verb is characteristic of Read category operations.
Attacks that exploit this kind of access
The rule that runs list_cron_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_cron_jobs, this is the rule to start with:
list_cron_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 Mcpg, apply this rule, and every list_cron_jobs call is checked against it from then on.
Questions about list_cron_jobs
list_cron_jobs is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for list_cron_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 Mcpg. Nothing to install.
list_cron_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 list_cron_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 list_cron_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.
list_cron_jobs is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue