compute_gravity_wall
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. In-situ mass concrete gravity retaining wall (typical C20/25 to C25/30) with trapezoidal cross...
This record as markdown: /tools/com-civilquants-civilquants/compute-gravity-wall.md
What compute_gravity_wall does on Civilquants
AI agents call compute_gravity_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 | Parameter form for a mass concrete gravity retaining wall. A single dataclass that — through combinations of its fields — produces all eight VARIANT_PRESETS pl |
standard | string | — | |
output_mode | string | — | |
deliverables | object | — |
Parameters from the server's own tool schema.
Why compute_gravity_wall is rated Low
This tool appears to perform parametric engineering calculations (estimating quantities for a gravity retaining wall) and return computed results. It is a read/query-style computation tool. While it mentions a 'paid tier' requiring authentication, the tool itself does not execute financial transactions — it merely gate-keeps access.
From the tool's definition 'Parametric estimating engine' and 'compute_gravity_wall' — the tool computes/calculates Bills of Quantities parameters for a gravity retaining wall assembly; no indication of data mutation, deletion, or financial transaction execution
Risk signalsHigh parameter count (33 properties)
Attacks that exploit this kind of access
The rule that runs compute_gravity_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_gravity_wall, this is the rule to start with:
compute_gravity_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_gravity_wall call is checked against it from then on.
Questions about compute_gravity_wall
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. In-situ mass concrete gravity retaining wall (typical C20/25 to C25/30) with trapezoidal cross-section, retaining soil by self-weight rather than structural action. Eight variant presets exercise the parameter form — landscape, highway boundary, trapezoidal, stepped-front, toe-projection, keyed-base, stepped-foundation, and battered-back-vertical-front. Routes via wall_type='gravity' attribute discrimination through CESMM4 F.5.3, NRM2 11.2.3, MMHW 1700.5 (SHW Cl. 1704 structural concrete), and SMM7 E10.2.3. Reinforcement default zero (gravity walls are nominally unreinforced); optional nominal face mesh available via nominal_face_reinforcement_kg_per_m3 parameter. Includes excavation (battered or supported, level or stepped foundation), blinding, drainage system (subsoil drain + granular surround + geotextile separator), Class 6N backfill, disposal, and formwork to vertical and battered faces. 13th use of the classed-then-legacy attribute discrimination pattern, and first use in the retaining wall family — opening the wall moat for subsequent counterfort (S30), anchored (S31) and bored pile (S32) variants. Example params: stem_height=3 m (1.5–6), stem_thickness_top=0.4 m (0.2–1), stem_thickness_bottom=1.3 m (0.4–2.5). Example call: {"params": {"stem_height": 3, "stem_thickness_top": 0.4, "stem_thickness_bottom": 1.3}, "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). It is categorised as a Read tool in the Civilquants MCP Server, which means it retrieves data without modifying state.
compute_gravity_wall accepts 4 parameters: params, standard, 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_gravity_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_gravity_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_gravity_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_gravity_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_gravity_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