# compute_utility_chamber Paid tier only. Calling this without an authenticated CivilQuants account returns TIER_INSUFFICIENT — sign up at https://civilquants.com/pricing or use the free-tier alternative compute_manhole. Catalogue-driven utility access chamber covering ten standard UK types: BT/Openreach jointing chambers JC1-JC4 (defaulting to UTILITY_PROVIDER_SUPPLY routing), water meter chamber (FW6), wastewater inspection chamber (RW9), valve chamber, gas Emergency Control Valve pit (ECV), LV electrical link box, and cable draw pit. Composite emission: precast chamber unit + BS EN 124 cover & frame (PC supply) + excavation + bedding (SHW Cl. 803) + granular surround + optional geotextile + selected fill + disposal. Routes via manhole_type=utility_chamber attribute discrimination through CESMM4 Class K.1.5.x, NRM2 33.7.11-.13, MMHW 500.5.13-.15 (SHW Cl. 507), and SMM7 R12.3.10-.12. JC types route their chamber unit through the v18 statutory-undertaker supply route infrastructure (CESMM4 Class A.4.3, NRM2 Group 1, MMHW Series 100, SMM7 A53) as a PC sum plus contractor attendance line. Example params: bedding_thickness_mm=150 mm (75–300), bedding_overhang_m=0.1 m (0.075–0.3), surround_thickness_m=0.15 m (0.1–0.3). Example call: {"params": {"bedding_thickness_mm": 150, "bedding_overhang_m": 0.1, "surround_thickness_m": 0.15}, "standard": "MMHW"}. Omitted parameters use sensible engineering defaults. Pass deliverables=["xlsx","dxf","pdf"] (any subset) to also receive one-shot download URLs in the same call: Excel BoQ (both tiers, watermarked free) plus the dimensioned DXF (CAD) and PDF drawing sheets (paid tier). Agent View of the PolicyLayer registry record for `compute_utility_chamber`. HTML page: https://policylayer.com/tools/com-civilquants-civilquants/compute-utility-chamber ## Facts - Tool: `compute_utility_chamber` - Server: Civilquants (`https://api.civilquants.com/mcp`) — https://policylayer.com/tools/com-civilquants-civilquants.md - Homepage: https://github.com/https://api.civilquants.com/mcp - Risk category: Execute (High risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 4 (1 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `params` | object | yes | Parameter form for a utility access chamber. Catalogue-driven: pick a ``chamber_type`` and the chamber's nominal plan dimensions, depth, wall thickness, cover | | `standard` | string | no | | | `output_mode` | string | no | | | `deliverables` | object | 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": "compute_utility_chamber", "arguments": { "params": {} } } } ``` ## Why compute_utility_chamber is rated High compute_utility_chamber triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up. Risk signals: High parameter count (27 properties) ## Use case AI agents invoke compute_utility_chamber to trigger actions in Civilquants. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Civilquants: ```json { "version": "1", "default": "deny", "tools": { "compute_utility_chamber": { "limits": [ { "counter": "compute_utility_chamber_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on Civilquants (55) - `compute_box_culvert` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-box-culvert.md - `compute_combined_services_trench` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-combined-services-trench.md - `compute_connection_to_existing` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-connection-to-existing.md - `compute_ditch` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-ditch.md - `compute_embankment_cross_section` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-embankment-cross-section.md - `compute_end_area_earthworks` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-end-area-earthworks.md - `compute_gabion_wall` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-gabion-wall.md - `compute_headwall_attenuation_outlet` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-headwall-attenuation-outlet.md - `compute_highway_drainage_channel` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-highway-drainage-channel.md - `compute_lighting_column` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-lighting-column.md - `compute_multi_section_assembly` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-multi-section-assembly.md - `compute_pad_foundation` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-pad-foundation.md - `compute_parapet` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-parapet.md - `compute_pipe_bedding` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-pipe-bedding.md - `compute_reinforced_soil_wall` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-reinforced-soil-wall.md - `compute_road_marking` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-road-marking.md - `compute_single_service_run` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-single-service-run.md - `compute_soakaway` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-soakaway.md - `compute_soil_nailed_slope` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-soil-nailed-slope.md - `compute_traffic_sign` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-traffic-sign.md - `compute_utility_kiosk_base` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-utility-kiosk-base.md - `recompute_project` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/recompute-project.md - `render_skill_report` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/render-skill-report.md - `compute_attenuation_tank` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-attenuation-tank.md - `compute_bored_pile_wall` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-bored-pile-wall.md - `compute_cantilever_wall` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-cantilever-wall.md - `compute_carrier_pipe_run` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-carrier-pipe-run.md - `compute_catchpit` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-catchpit.md - `compute_edge_drain` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-edge-drain.md - `compute_flexible_pavement` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-flexible-pavement.md - …and 25 more: https://policylayer.com/tools/com-civilquants-civilquants.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=com-civilquants-civilquants · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-civilquants-civilquants