calculate_cleaning_chemical_usage
Use this when a user needs a planning estimate for ready-to-use cleaning solution, concentrate, water, or generic container quantities across one or many jobs. It does not recommend brands and product-label directions always take precedence.
This record as markdown: /tools/11fgb-cleaning-tools-mcp/calculate-cleaning-chemical-usage.md
What calculate_cleaning_chemical_usage does on 11fgb Cleaning Tools
AI agents call calculate_cleaning_chemical_usage 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 |
|---|---|---|---|
jobs_count | integer | Yes | |
soil_level | string | — | |
postal_code | string | — | Optional US ZIP code for market context. |
cleaning_type | string | — | |
dilution_ratio | number | — | Parts water per one part concentrate, such as 64 for 1:64. |
reserve_percent | number | — | |
product_category | string | Yes | |
average_square_feet | integer | Yes | |
container_size_ounces | number | — | |
coverage_sqft_per_gallon | number | — |
Parameters from the server's own tool schema.
Why calculate_cleaning_chemical_usage is rated Low
Even though calculate_cleaning_chemical_usage 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 calculate_cleaning_chemical_usage 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 calculate_cleaning_chemical_usage, this is the rule to start with:
calculate_cleaning_chemical_usage 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 calculate_cleaning_chemical_usage call is checked against it from then on.
Questions about calculate_cleaning_chemical_usage
Use this when a user needs a planning estimate for ready-to-use cleaning solution, concentrate, water, or generic container quantities across one or many jobs. It does not recommend brands and product-label directions always take precedence. It is categorised as a Read tool in the 11fgb Cleaning Tools MCP Server, which means it retrieves data without modifying state.
calculate_cleaning_chemical_usage accepts 10 parameters: jobs_count, soil_level, postal_code, cleaning_type, dilution_ratio, reserve_percent, product_category, average_square_feet, container_size_ounces, coverage_sqft_per_gallon. Required: jobs_count, product_category, average_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 calculate_cleaning_chemical_usage: 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.
calculate_cleaning_chemical_usage 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 calculate_cleaning_chemical_usage 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 calculate_cleaning_chemical_usage. 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.
calculate_cleaning_chemical_usage 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