# compute_highway_drainage_channel

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_end_area_earthworks. Highway / surface-water drainage channel installation per BS EN 1433 + SHW Cl. 511-514 + HD 33/16. Discriminates between five UK channel product classifications via the channel_type enum (linear_polymer_concrete — ACO-pattern; linear_concrete — Charcon-pattern precast; slot_drain — narrow-slot recessed; combined_kerb_drainage — Beany/Safeticurb integrated unit per SHW Cl. 514; steel_grated_channel — heavy-duty stainless/galvanised). Plus parallel discriminators on two further WorkCategory entries: outfall_type on CHANNEL_OUTFALL (end / branch / side), silt_box_type on CHANNEL_SILT_BOX (standard / heavy-duty / deep-sump). The MMHW Series 500 _highway_drainage_channel handler is the platform's FOURTH 2D-banded handler — code 500.8.{t}.{d} bands by channel_type (5 bands) AND depth_class (4 bands). 5×4 = 20-cell grid. SMM7 routes to R12 (Drainage below ground) — SECOND highway L1 family outside Section Q after S39 lighting → V41. Example params: channel_depth_mm=100 mm (50–1500), channel_length_m=50 m (1–500), outfall_count=1 nr (0–20). Example call: {"params": {"channel_depth_mm": 100, "channel_length_m": 50, "outfall_count": 1}, "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_highway_drainage_channel`. HTML page: https://policylayer.com/tools/com-civilquants-civilquants/compute-highway-drainage-channel

## Facts

- Tool: `compute_highway_drainage_channel`
- 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 | Inputs for the highway_drainage_channel assembly. Required: channel_type — ChannelType enum (or string equivalent) depth_class — Depth |
| `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_highway_drainage_channel",
    "arguments": {
      "params": {}
    }
  }
}
```

## Why compute_highway_drainage_channel is rated High

compute_highway_drainage_channel 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 (13 properties)

## Use case

AI agents invoke compute_highway_drainage_channel 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_highway_drainage_channel": {
      "limits": [
        {
          "counter": "compute_highway_drainage_channel_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_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_chamber` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-utility-chamber.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