This record as markdown: /tools/io-github-devopam-mcpg/schedule-cron-job.md
What schedule_cron_job does on Mcpg
AI agents invoke schedule_cron_job to trigger actions in Mcpg. 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 schedule_cron_job is rated High
Scheduling a cron job means triggering recurring execution of commands or queries on the database server. This falls under Execute as it initiates automated, potentially broad operations. Severity is high because a misused cron job could repeatedly execute harmful queries, consume resources, or cause data corruption. Confidence is moderate due to the empty description.
From the tool's definition Tool name 'schedule_cron_job' implies scheduling and executing recurring jobs on the PostgreSQL server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs schedule_cron_job 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 schedule_cron_job, this is the rule to start with:
schedule_cron_job 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 Mcpg, apply this rule, and every schedule_cron_job call is checked against it from then on.
Questions about schedule_cron_job
schedule_cron_job is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpg MCP server in PolicyLayer and add a rule for schedule_cron_job: 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.
schedule_cron_job 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 schedule_cron_job 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 schedule_cron_job. 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.
schedule_cron_job 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