compute_cantilever_wall
Free tier. Renders the MMHW standard only — CESMM4, NRM2 and SMM7 require a paid tier. Anonymous callers welcome. In-situ reinforced concrete cantilever retaining wall with toe, heel, and stem. Includes excavation, blinding, drainage, and backfill quantities. Example params: stem_height=4 m (2–8)...
This record as markdown: /tools/com-civilquants-civilquants/compute-cantilever-wall.md
What compute_cantilever_wall does on Civilquants
AI agents call compute_cantilever_wall 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
params | object | Yes | |
standard | string | — | |
freeboard | object | — | |
output_mode | string | — | |
deliverables | object | — |
Parameters from the server's own tool schema.
Why compute_cantilever_wall is rated Low
This is a parametric estimating/calculation tool that generates Bills of Quantities output (numbers, spreadsheets, drawings) based on engineering parameters. It reads inputs and renders computed results. No data is written to a persistent store, no commands are executed, and no financial transactions occur. The 'deliverables' output (xlsx/dxf/pdf) is a read/render operation.
From the tool's definition 'Renders the MMHW standard only', 'Includes excavation, blinding, drainage, and backfill quantities' — the tool computes and returns quantity estimates/calculations; it does not create, modify, delete, or execute anything with external side effects.
Risk signalsHigh parameter count (23 properties)
Attacks that exploit this kind of access
The rule that runs compute_cantilever_wall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Civilquants, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compute_cantilever_wall, this is the rule to start with:
compute_cantilever_wall 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 Civilquants, apply this rule, and every compute_cantilever_wall call is checked against it from then on.
Questions about compute_cantilever_wall
Free tier. Renders the MMHW standard only — CESMM4, NRM2 and SMM7 require a paid tier. Anonymous callers welcome. In-situ reinforced concrete cantilever retaining wall with toe, heel, and stem. Includes excavation, blinding, drainage, and backfill quantities. Example params: stem_height=4 m (2–8), stem_thickness_top=0.3 m (0.2–0.6), stem_thickness_bottom=0.45 m (0.25–0.9). Example call: {"params": {"stem_height": 4, "stem_thickness_top": 0.3, "stem_thickness_bottom": 0.45}, "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). Pass freeboard (clearance below the wall top, m) instead of the retained-height field to set the retained fill by clearance — the engine back-calculates it as stem − freeboard. Supplying both is rejected. It is categorised as a Read tool in the Civilquants MCP Server, which means it retrieves data without modifying state.
compute_cantilever_wall accepts 5 parameters: params, standard, freeboard, output_mode, deliverables. Required: params. The full parameter table on this page comes from the server's own tool schema.
Register the Civilquants MCP server in PolicyLayer and add a rule for compute_cantilever_wall: 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 Civilquants. Nothing to install.
compute_cantilever_wall 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 compute_cantilever_wall 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 compute_cantilever_wall. 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.
compute_cantilever_wall is provided by the Civilquants MCP server (https://api.civilquants.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Civilquants, and thousands of servers like it.
This server
Across the catalogue