cronjob_create

Create a new cron job

SERVERNasbridge SOURCEmaverick0628/nasbridge

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nasbridge/cronjob-create.md

WHAT IT DOES

What cronjob_create does on Nasbridge

AI agents invoke cronjob_create to trigger actions in Nasbridge. 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.

RISK

Why cronjob_create is rated High

Creating a cron job schedules recurring execution of commands or scripts on the system. This enables arbitrary code execution on a schedule, making it an Execute-category action with high severity since a misused cron job could repeatedly run malicious or destructive commands.

From the tool's definition Create a new cron job

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cronjob_create safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cronjob_create, this is the rule to start with:

cronjob_create Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cronjob_create": {
      "limits": [
        {
          "counter": "cronjob_create_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every cronjob_create call is checked against it from then on.

FAQ

Questions about cronjob_create

What does the cronjob_create tool do? +

Create a new cron job. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cronjob_create? +

Register the Nasbridge MCP server in PolicyLayer and add a rule for cronjob_create: 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 Nasbridge. Nothing to install.

What risk level is cronjob_create? +

cronjob_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cronjob_create? +

Yes. Add a rate_limit block to the cronjob_create 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 cronjob_create completely? +

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

cronjob_create is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →