compute_combined_services_trench

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. Shared utility trench carrying multiple services side by side, each at its own cover depth (water, gas...

SERVERCivilquants SOURCEhttps://api.civilquants.com/mcp
High RISK CLASS
Category Execute
Parameters 41 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-combined-services-trench.md

What compute_combined_services_trench does on Civilquants

AI agents invoke compute_combined_services_trench 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.

ParameterTypeRequiredDescription
params object Yes
standard string
output_mode string
deliverables object

Parameters from the server's own tool schema.

Why compute_combined_services_trench is rated High

This tool executes a parametric computation engine that takes service parameters and generates detailed construction estimates and BoQ outputs. While it does not modify persistent state or delete data, it runs a non-trivial algorithm whose output (cost estimates, material quantities) directly informs financial decisions in civil engineering projects.

From the tool's definition "Calling this without an authenticated CivilQuants account returns TIER_INSUFFICIENT" indicates the tool performs paid computations that require account-gated access; "Renders through CESMM4 Class I, NRM2 Group 41..." shows it generates Bills of Quantities…

Risk signalsHigh parameter count (26 properties)

Questions about compute_combined_services_trench

What does the compute_combined_services_trench 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_manhole. Shared utility trench carrying multiple services side by side, each at its own cover depth (water, gas, electricity, telecoms) per NJUG Volume 1. One excavation envelope sized from the services, one disposal, one backfill column, with per-service lane-width bedding, surround, pipe/duct, and warning tape. Renders through CESMM4 Class I, NRM2 Group 41, MMHW Series 1300 and SMM7 Group T for the services, with the shared envelope routing through the existing earthworks/drainage handlers. Example params: trench_length_m=50 m (1–2000), service_spacing_mm=100 mm (50–500), working_space_below_bed_mm=100 mm (0–500). Example call: {"params": {"trench_length_m": 50, "service_spacing_mm": 100, "working_space_below_bed_mm": 100}, "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.

What parameters does compute_combined_services_trench accept? +

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

How do I enforce a policy on compute_combined_services_trench? +

Register the Civilquants MCP server in PolicyLayer and add a rule for compute_combined_services_trench: 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_combined_services_trench? +

compute_combined_services_trench is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit compute_combined_services_trench? +

Yes. Add a rate_limit block to the compute_combined_services_trench 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_combined_services_trench completely? +

Set action: deny in the PolicyLayer policy for compute_combined_services_trench. 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_combined_services_trench? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Civilquants's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.