compute_pipe_bedding

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-pipe-bedding.md

WHAT IT DOES

What compute_pipe_bedding does on Civilquants

AI agents invoke compute_pipe_bedding 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
`params`	object	Yes
`standard`	string	—
`output_mode`	string	—
`deliverables`	object	—

Parameters from the server's own tool schema.

RISK

Why compute_pipe_bedding is rated High

While the tool does not modify persistent data or delete anything, it executes complex estimating logic with configurable parameters that produce deterministic but non-trivial outputs (bills of quantities, trench specifications, cost implications). The output affects downstream civil engineering decisions and financial planning. It requires authentication and is paid-tier only, indicating material business logic.

From the tool's definition Tool 'compute_pipe_bedding' performs parametric estimation calculations ('Emits trench excavation, granular bed, surround or concrete cradle/encasement, selected backfill, disposal and pipework').

Risk signalsHigh parameter count (18 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

compute_pipe_bedding Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compute_pipe_bedding": {
      "limits": [
        {
          "counter": "compute_pipe_bedding_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_pipe_bedding call is checked against it from then on.

FAQ

Questions about compute_pipe_bedding

What does the compute_pipe_bedding 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. Linear pipe trench with class-driven bedding and surround. Strategy pattern on (BeddingContext × BeddingClass): Highway (HA 40/01 / MMHW Series 500) vs Building (BS EN 1610 / NRM2 §33), Class N/F/B/S/A/Z. Emits trench excavation, granular bed, surround or concrete cradle/encasement, selected backfill, disposal and pipework. All four standards render with class and clause references. Example params: pipe_internal_diameter_mm=300 mm (100–1800), pipe_wall_thickness_mm=50 mm (10–200), pipe_length=25 m (1–500). Example call: {"params": {"pipe_internal_diameter_mm": 300, "pipe_wall_thickness_mm": 50, "pipe_length": 25}, "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_pipe_bedding accept? +

compute_pipe_bedding 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_pipe_bedding? +

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

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

Can I rate-limit compute_pipe_bedding? +

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

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

compute_pipe_bedding 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →