vacuum_start

Start a new whole-home cleaning job. Use vacuum_pause with paused=false to resume.

SERVERTolpo SOURCEsignerless/tolpo

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What vacuum_start does on Tolpo

AI agents invoke vacuum_start to trigger actions in Tolpo. 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.

RISK

Why vacuum_start is rated High

vacuum_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vacuum_start 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_start, this is the rule to start with:

vacuum_start Rate-limited

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vacuum_start

What does the vacuum_start tool do? +

Start a new whole-home cleaning job. Use vacuum_pause with paused=false to resume. It is categorised as a Execute tool in the Tolpo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vacuum_start? +

Register the Tolpo MCP server in PolicyLayer and add a rule for vacuum_start: 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_start? +

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

Can I rate-limit vacuum_start? +

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

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

vacuum_start 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 → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →