compute_strip_foundation
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 reinforced concrete strip foundation, level or stepped. Closes the P1 launch set alongs...
This record as markdown: /tools/com-civilquants-civilquants/compute-strip-foundation.md
What compute_strip_foundation does on Civilquants
AI agents use compute_strip_foundation 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 | Parameters for the strip foundation assembly. Defaults are tuned to a typical UK domestic / light commercial strip: 750mm wide, 350mm deep, 10m long, founded ~ |
standard | string | — | |
output_mode | string | — | |
deliverables | object | — |
Parameters from the server's own tool schema.
Why compute_strip_foundation is rated Medium
An AI agent can call compute_strip_foundation 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 (22 properties)
Attacks that exploit this kind of access
The rule that runs compute_strip_foundation 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_strip_foundation, this is the rule to start with:
compute_strip_foundation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Civilquants, apply this rule, and every compute_strip_foundation call is checked against it from then on.
Questions about compute_strip_foundation
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 reinforced concrete strip foundation, level or stepped. Closes the P1 launch set alongside pad_foundation. Integrates BS 8666:2020 reinforcement scheduling. Stepping is the v10 demonstration of cross-cutting standards-handler discrimination. Example params: length=10 m (1–100), width=0.75 m (0.3–2.5), thickness=0.35 m (0.15–1.5). Example call: {"params": {"length": 10, "width": 0.75, "thickness": 0.35}, "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 Write tool in the Civilquants MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
compute_strip_foundation 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_strip_foundation: 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_strip_foundation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the compute_strip_foundation 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_strip_foundation. 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_strip_foundation 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