vacuum_map

Read one map's metadata and its room ids, names and preferences. The bitmap is not decoded or returned.

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-map.md

WHAT IT DOES

What vacuum_map does on Tolpo

AI agents call vacuum_map 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_map is rated Low

Even though vacuum_map 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vacuum_map Allowed

vacuum_map 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_map": {}
  }
}

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_map call is checked against it from then on.

FAQ

Questions about vacuum_map

What does the vacuum_map tool do? +

Read one map's metadata and its room ids, names and preferences. The bitmap is not decoded or returned. 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_map? +

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

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

Can I rate-limit vacuum_map? +

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

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

vacuum_map 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

The MCP Attack Database →

Guides

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