create_cronjob
A execute tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/create-cronjob.md
What create_cronjob does on 1Panel MCP Server
AI agents invoke create_cronjob to trigger actions in 1Panel 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 create_cronjob is rated High
Creating a cronjob schedules arbitrary code or commands to execute repeatedly on the server. While the creation act itself is a Write, the primary purpose and effect is to trigger recurring execution of operations, making it an Execute-category tool. Misuse could lead to persistent malicious command execution, giving it high severity.
From the tool's definition 'Create cronjob' - creates a scheduled job that will execute commands/scripts automatically on a recurring basis
Attacks that exploit this kind of access
The rule that runs create_cronjob safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_cronjob, this is the rule to start with:
create_cronjob 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 1Panel MCP Server, apply this rule, and every create_cronjob call is checked against it from then on.
Questions about create_cronjob
create_cronjob is a execute tool on the 1Panel MCP Server MCP server. It is categorised as a Execute tool in the 1Panel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for create_cronjob: 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 1Panel MCP Server. Nothing to install.
create_cronjob 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 create_cronjob 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 create_cronjob. 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.
create_cronjob is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
Across the catalogue