Critical Risk →

goclaw_cron_delete

Delete a cron job

How to control goclaw_cron_delete ↓

What goclaw_cron_delete does on GoClaw MCP Server

AI agents call goclaw_cron_delete to permanently remove resources in GoClaw MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why goclaw_cron_delete needs a policy

Deleting a cron job is a destructive action that cannot be undone and stops recurring operations. In an enterprise gateway infrastructure context (per server description), removing cron jobs could disrupt critical automated processes, monitoring, or maintenance tasks. This warrants the Destructive category and high severity due to potential operational impact.

From the tool's definition Tool name contains 'delete' and description states 'Delete a cron job' — this irreversibly removes a scheduled automation task.

Documented attack patterns abuse exactly the kind of access goclaw_cron_delete gives an agent:

How to control goclaw_cron_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and GoClaw MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for goclaw_cron_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "goclaw_cron_delete"
  ]
}

goclaw_cron_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GoClaw MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about goclaw_cron_delete

What does the goclaw_cron_delete tool do? +

Delete a cron job. It is categorised as a Destructive tool in the GoClaw MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on goclaw_cron_delete? +

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

What risk level is goclaw_cron_delete? +

goclaw_cron_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit goclaw_cron_delete? +

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

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

goclaw_cron_delete is provided by the GoClaw MCP Server MCP server (nextlevelbuilder/goclaw-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoClaw MCP Server tool call.

Start from GoClaw MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

66 GoClaw MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.