compute_connection_to_existing
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_manhole. Enumerated extra-over connection of a new drainage carrier pipe into an existing asset: existing manho...
This record as markdown: /tools/com-civilquants-civilquants/compute-connection-to-existing.md
What compute_connection_to_existing does on Civilquants
AI agents invoke compute_connection_to_existing 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 |
|---|---|---|---|
params | object | Yes | Parameters for a single connection-to-existing extra-over item. |
standard | string | — | |
output_mode | string | — | |
deliverables | object | — |
Parameters from the server's own tool schema.
Why compute_connection_to_existing is rated High
This tool executes a parametric calculation engine that generates construction Bills of Quantities—binding cost estimates used in civils engineering contracts. While no data is deleted and no financial transaction occurs directly, the tool's output (quantified scope of works tied to pricing standards) triggers downstream financial and contractual obligations when used in professional estimating workflows.
From the tool's definition compute_connection_to_existing; description states the tool computes Bills of Quantities for drainage infrastructure connections using standardized estimation routes (CESMM4, NRM2, MMHW).
Attacks that exploit this kind of access
The rule that runs compute_connection_to_existing 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_connection_to_existing, this is the rule to start with:
compute_connection_to_existing 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_connection_to_existing call is checked against it from then on.
Questions about compute_connection_to_existing
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_manhole. Enumerated extra-over connection of a new drainage carrier pipe into an existing asset: existing manhole / inspection chamber, existing sewer or drain (via saddle / wye / cut-in junction), or existing outfall / watercourse / surface system. Routes via CESMM4 I.7.1/2/3 (Class I §I.7 Pipework Ancillaries — Connections), NRM2 33.6.1/2/3, MMHW 500.5.1/2/3 (SHW Cl. 506 Connections to existing sewers, drains and service runs), SMM7 R12.4.1/2/3, with a bore-size digit suffix appended in all four. The connection_type attribute is the discriminator that routes to the right sub-code; the bore digit refines within. Six variant presets cover all three connection types × two characteristic bores. Unit: Nr. Opens the new drainage_ancillaries L2 leaf (reserved for ditch, hard-material extra-over, CCTV testing, etc. in future sessions). Sibling assembly: carrier_pipe_run — the S32 pair that delivers a complete tender drainage line. Example params: diameter_mm=225 mm (100–2400). Example call: {"params": {"diameter_mm": 225}, "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 Execute tool in the Civilquants MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
compute_connection_to_existing 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_connection_to_existing: 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_connection_to_existing 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_connection_to_existing 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_connection_to_existing. 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_connection_to_existing 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