create_cron · ClawDaemon MCP: Risk & Policy

WHAT IT DOES

What create_cron does on ClawDaemon MCP

AI agents invoke create_cron to trigger actions in ClawDaemon MCP. 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 IT NEEDS A POLICY

Why create_cron needs a policy

This tool creates scheduled recurring automations that execute on a cron schedule via a persistent background daemon. The key risk is that it can trigger repeated, automated operations (browser automation, webhooks, messaging across 23+ platforms) indefinitely, even after the Claude session ends.

From the tool's definition "Create a recurring automation that runs on a cron schedule" — schedules and triggers automated executions on a persistent daemon

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_cron Rate-limited

create_cron 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": {
    "create_cron": {
      "limits": [
        {
          "counter": "create_cron_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_cron

What does the create_cron tool do? +

Create a recurring automation that runs on a cron schedule. It is categorised as a Execute tool in the ClawDaemon MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_cron? +

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

What risk level is create_cron? +

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

Can I rate-limit create_cron? +

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

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

create_cron is provided by the ClawDaemon MCP server (mordiaky/clawdaemon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.