High Risk →

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 at staggered depths (water, gas, electricity, telecom...

Risk signalsHigh parameter count (25 properties)

Part of the Civilquants server.

compute_combined_services_trench can trigger actions in Civilquants, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CIVILQUANTS →

Free to start. No card required.

AI agents invoke compute_combined_services_trench to trigger processes or run actions in Civilquants. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

compute_combined_services_trench can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "compute_combined_services_trench": {
      "limits": [
        {
          "counter": "compute_combined_services_trench_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Civilquants policy for all 52 tools.

Get this rule live on your own Civilquants server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CIVILQUANTS →

View all 52 tools →

These attack patterns abuse exactly the kind of access compute_combined_services_trench gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so compute_combined_services_trench only ever does what you allow.

SECURE CIVILQUANTS →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

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 at staggered depths (water, gas, electricity, telecoms) per NJUG Volume 1. One excavation envelope, one disposal, one backfill column, with per-service 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), trench_width_m=0.9 m (0.3–3), working_space_below_bed_mm=100 mm (0–500). Example call: {"params": {"trench_length_m": 50, "trench_width_m": 0.9, "working_space_below_bed_mm": 100}, "standard": "MMHW"}. Omitted parameters use sensible engineering defaults. Pass deliverables=["xlsx"] to also receive a one-shot Excel BoQ download URL in the same call.. 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.

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.

Enforce policy on every Civilquants tool call.

Deterministic rules across all 52 Civilquants tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.