estimate_cleaning_time_and_crew
Use this when a user asks how long a cleaning job may take or how many cleaners are needed. Works for homes, apartments, offices, retail, and vacation rentals. It estimates workload, not worker availability or a price quote.
This record as markdown: /tools/11fgb-cleaning-tools-mcp/estimate-cleaning-time-and-crew.md
What estimate_cleaning_time_and_crew does on 11fgb Cleaning Tools
AI agents call estimate_cleaning_time_and_crew to retrieve information from 11fgb Cleaning Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
bathrooms | number | — | |
condition | string | — | |
postal_code | string | — | Optional US ZIP code. It affects the market label, not cleaning time. |
square_feet | integer | Yes | |
cleaning_type | string | — | |
property_type | string | Yes | |
rooms_or_zones | integer | — | |
max_visit_hours | number | — |
Parameters from the server's own tool schema.
Why estimate_cleaning_time_and_crew is rated Low
Even though estimate_cleaning_time_and_crew 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
The rule that runs estimate_cleaning_time_and_crew safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 11fgb Cleaning Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For estimate_cleaning_time_and_crew, this is the rule to start with:
estimate_cleaning_time_and_crew is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 11fgb Cleaning Tools, apply this rule, and every estimate_cleaning_time_and_crew call is checked against it from then on.
Questions about estimate_cleaning_time_and_crew
Use this when a user asks how long a cleaning job may take or how many cleaners are needed. Works for homes, apartments, offices, retail, and vacation rentals. It estimates workload, not worker availability or a price quote. It is categorised as a Read tool in the 11fgb Cleaning Tools MCP Server, which means it retrieves data without modifying state.
estimate_cleaning_time_and_crew accepts 8 parameters: bathrooms, condition, postal_code, square_feet, cleaning_type, property_type, rooms_or_zones, max_visit_hours. Required: square_feet, property_type. The full parameter table on this page comes from the server's own tool schema.
Register the 11fgb Cleaning Tools MCP server in PolicyLayer and add a rule for estimate_cleaning_time_and_crew: 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 11fgb Cleaning Tools. Nothing to install.
estimate_cleaning_time_and_crew is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the estimate_cleaning_time_and_crew 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.
Set action: deny in the PolicyLayer policy for estimate_cleaning_time_and_crew. 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.
estimate_cleaning_time_and_crew is provided by the 11fgb Cleaning Tools MCP server (kossik/11fgb-cleaning-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 11fgb Cleaning Tools, and thousands of servers like it.
This server
Across the catalogue