estimate_home_cleaning_cost
Use this when a user wants a free planning estimate for cleaning a US house, apartment, condo, or townhouse. Returns price range, labor hours, crew size, duration, assumptions, and a visual report. Do not present it as a binding quote.
This record as markdown: /tools/11fgb-cleaning-tools-mcp/estimate-home-cleaning-cost.md
What estimate_home_cleaning_cost does on 11fgb Cleaning Tools
AI agents call estimate_home_cleaning_cost 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 |
|---|---|---|---|
pets | integer | — | |
add_ons | array | — | |
bedrooms | integer | — | |
bathrooms | number | — | |
condition | string | — | |
frequency | string | — | |
postal_code | string | Yes | US ZIP code used to select local or national rates. |
square_feet | integer | Yes | Total interior square footage. |
cleaning_type | string | — | |
property_type | string | — |
Parameters from the server's own tool schema.
Why estimate_home_cleaning_cost is rated Low
Even though estimate_home_cleaning_cost 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 signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs estimate_home_cleaning_cost 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_home_cleaning_cost, this is the rule to start with:
estimate_home_cleaning_cost 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_home_cleaning_cost call is checked against it from then on.
Questions about estimate_home_cleaning_cost
Use this when a user wants a free planning estimate for cleaning a US house, apartment, condo, or townhouse. Returns price range, labor hours, crew size, duration, assumptions, and a visual report. Do not present it as a binding quote. It is categorised as a Read tool in the 11fgb Cleaning Tools MCP Server, which means it retrieves data without modifying state.
estimate_home_cleaning_cost accepts 10 parameters: pets, add_ons, bedrooms, bathrooms, condition, frequency, postal_code, square_feet, cleaning_type, property_type. Required: postal_code, square_feet. 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_home_cleaning_cost: 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_home_cleaning_cost 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_home_cleaning_cost 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_home_cleaning_cost. 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_home_cleaning_cost 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