compute_counterfort_wall

SERVERCivilquants SOURCEhttps://api.civilquants.com/mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-civilquants-civilquants/compute-counterfort-wall.md

WHAT IT DOES

What compute_counterfort_wall does on Civilquants

AI agents use compute_counterfort_wall to create or update resources in Civilquants, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Civilquants environment.

Parameter	Type	Required	Description
`params`	object	Yes	Parameter form for an in-situ RC counterfort retaining wall. A single dataclass that — through combinations of its fields — produces all eight VARIANT_PRESETS
`standard`	string	—
`freeboard`	object	—
`output_mode`	string	—
`deliverables`	object	—

Parameters from the server's own tool schema.

RISK

Why compute_counterfort_wall is rated Medium

An AI agent can call compute_counterfort_wall faster than any human can review: one bad instruction and it creates or modifies resources in Civilquants by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (34 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compute_counterfort_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_counterfort_wall, this is the rule to start with:

compute_counterfort_wall Rate-limited

compute_counterfort_wall stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compute_counterfort_wall": {
      "limits": [
        {
          "counter": "compute_counterfort_wall_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Civilquants, apply this rule, and every compute_counterfort_wall call is checked against it from then on.

FAQ

Questions about compute_counterfort_wall

What does the compute_counterfort_wall tool do? +

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 reinforced concrete counterfort retaining wall. Discrete RC counterforts on the retained face enhance moment capacity, making the wall economic for 4-10m retained heights (above cantilever-economic range, below anchored-wall range). Includes base slab, thin curtain wall, counterforts at configurable centres, drainage, and backfill. Eight VARIANT_PRESETS exercise the 'one parameter form, eight variants, four standards' moat #1 claim. Routes via wall_type='counterfort' attribute discrimination: CESMM4 F.6.3, NRM2 11.3.3, MMHW 1700.4.2 (SHW Cl. 1704), SMM7 E10.3.2. Example params: stem_height=5 m (3–12), curtain_thickness=0.35 m (0.2–0.6), toe_length=0.6 m (0–3). Example call: {"params": {"stem_height": 5, "curtain_thickness": 0.35, "toe_length": 0.6}, "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 Write tool in the Civilquants MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does compute_counterfort_wall accept? +

compute_counterfort_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.

How do I enforce a policy on compute_counterfort_wall? +

Register the Civilquants MCP server in PolicyLayer and add a rule for compute_counterfort_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.

What risk level is compute_counterfort_wall? +

compute_counterfort_wall is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit compute_counterfort_wall? +

Yes. Add a rate_limit block to the compute_counterfort_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.

How do I block compute_counterfort_wall completely? +

Set action: deny in the PolicyLayer policy for compute_counterfort_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.

What MCP server provides compute_counterfort_wall? +

compute_counterfort_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.

KEEP EXPLORING

More on Civilquants, and thousands of servers like it.

This server

All 56 Civilquants tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →