compute_lighting_column
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_end_area_earthworks. Highway / street lighting column installation per BS EN 40 + BS 5489-1:2020 + TR 22. Discr...
This record as markdown: /tools/com-civilquants-civilquants/compute-lighting-column.md
What compute_lighting_column does on Civilquants
AI agents invoke compute_lighting_column 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 | Inputs for the lighting_column assembly. Defaults anchored to URBAN_6M_LED — UK urban distributor: 6 m steel galvanised column on precast socket, BS EN 40-3 Cl |
standard | string | — | |
output_mode | string | — | |
deliverables | object | — |
Parameters from the server's own tool schema.
Why compute_lighting_column is rated High
The tool invokes a remote parametric estimating engine that performs computation and returns structured cost/quantity data. It is not purely a read (it processes inputs and executes a calculation workflow on a paid external service), but it does not write, delete, or move money — it executes a calculation. The financial-tier gate is an access control mechanism, not a financial transaction itself.
From the tool's definition 'Paid tier only. Calling this without an authenticated CivilQuants account returns TIER_INSUFFICIENT' and 'compute_lighting_column' — triggers a parametric estimating computation against a remote authenticated service, discriminating on multiple enums…
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs compute_lighting_column 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_lighting_column, this is the rule to start with:
compute_lighting_column 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_lighting_column call is checked against it from then on.
Questions about compute_lighting_column
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_end_area_earthworks. Highway / street lighting column installation per BS EN 40 + BS 5489-1:2020 + TR 22. Discriminates between four UK column material classifications via the column_type enum (steel_galvanised, aluminium, composite_grp, decorative_cast_iron). Plus parallel discriminators on three further WorkCategory entries: foundation_type on COLUMN_FOUNDATION, luminaire_type on LUMINAIRE, bracket_type on COLUMN_BRACKET. The MMHW Series 1300 _lighting_column handler is the platform's THIRD 2D-banded handler — code 1300.4.1.{h}.{c} bands by column_height_class (6 bands per TR 22) AND column_loading_class (4 bands per BS EN 40-3). 6×4 = 24-cell grid (the LARGEST banded grid in the platform). Example params: mounting_height_m=6 m (4–16), luminaire_wattage_W=60 W (10–1000), bracket_count=0 Nr (0–4). Example call: {"params": {"mounting_height_m": 6, "luminaire_wattage_W": 60, "bracket_count": 0}, "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_lighting_column 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_lighting_column: 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_lighting_column 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_lighting_column 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_lighting_column. 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_lighting_column 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