compute_multi_section_assembly
Compute one sectioned/linear assembly across multiple sections in a single call and return a combined Bill of Quantities plus per-section results. Each section sets its own run_length and geometry; shared_params apply to all sections. Use for a wall, kerb run, drain or barrier that changes along ...
This record as markdown: /tools/com-civilquants-civilquants/compute-multi-section-assembly.md
What compute_multi_section_assembly does on Civilquants
AI agents invoke compute_multi_section_assembly to trigger actions in Civilquants. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
sections | array | Yes | |
standard | string | — | |
deliverables | object | — | |
aggregate_boq | boolean | — | |
assembly_slug | string | Yes | |
shared_params | object | — | |
include_backup | boolean | — | |
include_section_boq | boolean | — |
Parameters from the server's own tool schema.
Why compute_multi_section_assembly is rated High
The tool triggers execution of a complex parametric calculation engine that processes civil engineering assembly definitions and geometric parameters to produce Bills of Quantities across multiple sections. While not executing arbitrary code, it performs non-trivial computations whose outputs directly influence cost estimates and material requirements for construction projects.
From the tool's definition Tool name 'compute_multi_section_assembly' performs computational operations; description states it 'Compute one sectioned/linear assembly across multiple sections in a single call and return a combined Bill of Quantities'.
Attacks that exploit this kind of access
The rule that runs compute_multi_section_assembly 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_multi_section_assembly, this is the rule to start with:
compute_multi_section_assembly stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_multi_section_assembly call is checked against it from then on.
Questions about compute_multi_section_assembly
Compute one sectioned/linear assembly across multiple sections in a single call and return a combined Bill of Quantities plus per-section results. Each section sets its own run_length and geometry; shared_params apply to all sections. Use for a wall, kerb run, drain or barrier that changes along its length. assembly_slug must be a sectioned assembly (e.g. cantilever_wall, kerb_run, edge_drain); non-linear items return INVALID_INPUT. Free tier: MMHW only, each section consumes one daily slot. Example: {"assembly_slug":"cantilever_wall","standard":"MMHW","sections":[{"label":"Bay 1","run_length":20,"stem_height":1.5},{"label":"Bay 2","run_length":15,"stem_height":2.4}]}. It is categorised as a Execute tool in the Civilquants MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
compute_multi_section_assembly accepts 8 parameters: sections, standard, deliverables, aggregate_boq, assembly_slug, shared_params, include_backup, include_section_boq. Required: sections, assembly_slug. 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_multi_section_assembly: 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_multi_section_assembly is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the compute_multi_section_assembly 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_multi_section_assembly. 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_multi_section_assembly 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.
Across the catalogue