# compute_kerb_run 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_cantilever_wall. Linear precast concrete kerb run on concrete bed and haunch over Type 1 (Class 1A) granular sub-base. Emits excavation, sub-base (v8 SHW-class-aware), concrete bed, kerb units to BS EN 1340 / SHW Cl. 1101, concrete haunch to back face, optional channel block, and disposal. Supports HB2/HB1/SP/BN/EF/ER kerb profiles and CS1/CS2/dish channels. All four standards render with type designators (CESMM4 R.7, NRM2 34.10, MMHW 1100, SMM7 Q10). Example params: kerb_length=25 m (1–1000), bed_thickness_mm=150 mm (75–300), bed_extra_each_side_mm=100 mm (0–300). Example call: {"params": {"kerb_length": 25, "bed_thickness_mm": 150, "bed_extra_each_side_mm": 100}, "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_kerb_run`. HTML page: https://policylayer.com/tools/com-civilquants-civilquants/compute-kerb-run ## Facts - Tool: `compute_kerb_run` - 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: Read (Low risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 4 (1 required) - Recommended policy verdict: Allowed ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `params` | object | yes | Input parameters for a kerb run assembly. Geometric defaults match a standard UK HB2 road kerb on 150mm concrete bed over 150mm Type 1 sub-base, with triangula | | `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_kerb_run", "arguments": { "params": {} } } } ``` ## Why compute_kerb_run is rated Low This is a parametric estimating/computation tool that calculates and emits bill-of-quantities line items for a kerb run assembly. It reads inputs and outputs cost/quantity data — it does not write to a database, execute code, delete data, or move money. The 'paid tier' gate is an authentication concern, not a financial transaction made by the tool itself. From the tool's own definition: "Paid tier only... Emits excavation, sub-base... concrete bed, kerb units... disposal. Supports HB2/HB1/SP/BN/EF/ER kerb profiles" Risk signals: High parameter count (16 properties) ## Use case AI agents call compute_kerb_run to retrieve information from Civilquants 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 Civilquants: ```json { "version": "1", "default": "deny", "tools": { "compute_kerb_run": {} } } ``` ## 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_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 - …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