# 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.

Agent View of the PolicyLayer registry record for `calculate_cleaning_chemical_usage`. HTML page: https://policylayer.com/tools/11fgb-cleaning-tools-mcp/calculate-cleaning-chemical-usage

## Facts

- Tool: `calculate_cleaning_chemical_usage`
- Server: 11fgb Cleaning Tools (`kossik/11fgb-cleaning-tools-mcp`) — https://policylayer.com/tools/11fgb-cleaning-tools-mcp.md
- Homepage: https://github.com/kossik/11fgb-cleaning-tools-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 10 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `jobs_count` | integer | yes |  |
| `soil_level` | string | no |  |
| `postal_code` | string | no | Optional US ZIP code for market context. |
| `cleaning_type` | string | no |  |
| `dilution_ratio` | number | no | Parts water per one part concentrate, such as 64 for 1:64. |
| `reserve_percent` | number | no |  |
| `product_category` | string | yes |  |
| `average_square_feet` | integer | yes |  |
| `container_size_ounces` | number | no |  |
| `coverage_sqft_per_gallon` | number | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "calculate_cleaning_chemical_usage",
    "arguments": {
      "jobs_count": 0,
      "product_category": "<product_category>",
      "average_square_feet": 0
    }
  }
}
```

## 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 signals: High parameter count (10 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 11fgb Cleaning Tools:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "calculate_cleaning_chemical_usage": {}
  }
}
```

## Other tools on 11fgb Cleaning Tools (3)

- `estimate_cleaning_time_and_crew` — Read — https://policylayer.com/tools/11fgb-cleaning-tools-mcp/estimate-cleaning-time-and-crew.md
- `estimate_home_cleaning_cost` — Read — https://policylayer.com/tools/11fgb-cleaning-tools-mcp/estimate-home-cleaning-cost.md
- `estimate_office_cleaning_cost` — Read — https://policylayer.com/tools/11fgb-cleaning-tools-mcp/estimate-office-cleaning-cost.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=11fgb-cleaning-tools-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/11fgb-cleaning-tools-mcp