vacuum_remove_schedule

Remove one schedule. Does not remove all schedules.

SERVERTolpo SOURCEsignerless/tolpo

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tolpo/vacuum-remove-schedule.md

WHAT IT DOES

What vacuum_remove_schedule does on Tolpo

AI agents call vacuum_remove_schedule to permanently remove resources in Tolpo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why vacuum_remove_schedule is rated Critical

An AI agent that decides to call vacuum_remove_schedule doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Tolpo is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vacuum_remove_schedule safely

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

vacuum_remove_schedule Hidden

vacuum_remove_schedule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vacuum_remove_schedule

What does the vacuum_remove_schedule tool do? +

Remove one schedule. Does not remove all schedules. It is categorised as a Destructive tool in the Tolpo 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 vacuum_remove_schedule? +

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

What risk level is vacuum_remove_schedule? +

vacuum_remove_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 vacuum_remove_schedule? +

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

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

vacuum_remove_schedule is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tolpo, and thousands of servers like it.

This server

All 243 Tolpo tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →