delete_schedule

THE RISK

Critical Risk

Why delete_schedule needs a policy

This tool permanently removes a scheduled task configuration, which cannot be undone. Once deleted, the recurring maintenance task will no longer execute. While the data loss is limited to task metadata rather than source code or user data, the action is irreversible and could disrupt critical maintenance automation that an organization depends on.

From the tool's definition Tool name 'delete_schedule' combined with description 'Delete a scheduled task by name' indicates irreversible deletion of a scheduled automation task.

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

POLICY

How to control delete_schedule

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_schedule"
  ]
}

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

Create a free account and register Jules MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jules MCP Server tools

Destructive delete_session Delete or cancel an active Jules session Execute create_coding_task Creates a new Jules coding session. Returns immediately with a session ID. Monitor progres Execute create_repoless_task Creates a new Jules session without repository context for scripts, prototypes, or researc Execute manage_session Manage an active Jules session: approve or reject plans, or send feedback Execute schedule_recurring_task Schedule a Jules task to run automatically on a cron schedule. The server manages executio Read wait_for_session Poll a Jules session until it reaches a target state or the timeout expires Read get_activities_since Get session activities newer than a provided ISO timestamp Read get_session_status Get the current status and state of a Jules session

All 11 Jules MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Jules MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_schedule

What does the delete_schedule tool do? +

Delete a scheduled task by name. It is categorised as a Destructive tool in the Jules 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 delete_schedule? +

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

What risk level is delete_schedule? +

delete_schedule 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 delete_schedule? +

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

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

delete_schedule is provided by the Jules MCP Server MCP server (savethepolarbears/jules-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jules MCP Server tool call.

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

CHECK YOUR STACK →