vacuum_status

Read status, every reported error and prompt, battery and cleaning progress.

SERVERTolpo SOURCEsignerless/tolpo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What vacuum_status does on Tolpo

AI agents call vacuum_status to retrieve information from Tolpo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why vacuum_status is rated Low

Even though vacuum_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vacuum_status Allowed

vacuum_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vacuum_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vacuum_status

What does the vacuum_status tool do? +

Read status, every reported error and prompt, battery and cleaning progress. It is categorised as a Read tool in the Tolpo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vacuum_status? +

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

vacuum_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vacuum_status? +

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

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

vacuum_status 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 →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →