cron_scaffold_job · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What cron_scaffold_job does on LaunchFrame MCP

AI agents use cron_scaffold_job to create or update resources in LaunchFrame MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LaunchFrame MCP environment.

WHY IT NEEDS A POLICY

Why cron_scaffold_job needs a policy

The tool scaffolds (generates) a new cron job method that will be added to an existing service file. This is a reversible write operation—the generated code can be deleted or modified. It does not execute the job, only creates the scaffolding for it. While it modifies the codebase structure, this is a code generation task rather than an irreversible deletion or actual execution of side effects.

From the tool's definition Tool name 'cron_scaffold_job' and description 'Scaffold a new cron method to add to CronService' indicate generation of new code that will be added to a file (src/jobs/cron.service.ts). This is a write operation as it creates new code content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cron_scaffold_job Rate-limited

cron_scaffold_job stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cron_scaffold_job": {
      "limits": [
        {
          "counter": "cron_scaffold_job_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LaunchFrame MCP, so you can run agents against it safely.

FAQ

Questions about cron_scaffold_job

What does the cron_scaffold_job tool do? +

Scaffold a new cron method to add to CronService (src/jobs/cron.service.ts). It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cron_scaffold_job? +

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

What risk level is cron_scaffold_job? +

cron_scaffold_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cron_scaffold_job? +

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

How do I block cron_scaffold_job completely? +

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

What MCP server provides cron_scaffold_job? +

cron_scaffold_job is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.