PIPEINSUL
Calculate optimal pipe insulation thickness to limit outer surface temperature (burn protection) and minimise heat loss. Uses cylindrical heat conduction + external convection model, solved via scipy.optimize.brentq. Returns exact minimum thickness and nearest commercial 5 mm step.
This record as markdown: /tools/com-engscript-mcp/pipeinsul.md
What PIPEINSUL does on EngScript Engineering MCP
AI agents call PIPEINSUL as a supporting operation in EngScript Engineering MCP workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
Ta | object | Yes | Ambient (outdoor) temperature |
Tf | object | Yes | Fluid / pipe outer surface temperature |
ha | object | Yes | External (air-side) convection coefficient |
NPS | object | Yes | Nominal Pipe Size in inches (ASME B36.10). |
Tmax | object | Yes | Maximum allowable insulation outer surface temperature (burn-prevention limit = 50 °C per EN ISO 13732-1) |
kins | object | Yes | Insulation thermal conductivity |
r2_unit | string | — | Desired Pipe outer radius output unit |
r3_unit | string | — | Desired Insulation outer radius output unit |
tins_unit | string | — | Desired Insulation thickness output unit |
Dpipe_unit | string | — | Desired Pipe OD output unit |
Qloss_unit | string | — | Desired Heat loss output unit |
Tsurf_unit | string | — | Desired Surface temperature output unit |
Parameters from the server's own tool schema.
Why PIPEINSUL is rated Low
Without any rule in front of it, every call an agent makes to PIPEINSUL happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Risk signalsHigh parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs PIPEINSUL safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EngScript Engineering MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For PIPEINSUL, this is the rule to start with:
PIPEINSUL gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EngScript Engineering MCP, apply this rule, and every PIPEINSUL call is checked against it from then on.
Questions about PIPEINSUL
Calculate optimal pipe insulation thickness to limit outer surface temperature (burn protection) and minimise heat loss. Uses cylindrical heat conduction + external convection model, solved via scipy.optimize.brentq. Returns exact minimum thickness and nearest commercial 5 mm step. It is categorised as a Other tool in the EngScript Engineering MCP MCP Server, which means it performs auxiliary operations.
PIPEINSUL accepts 12 parameters: Ta, Tf, ha, NPS, Tmax, kins, r2_unit, r3_unit, tins_unit, Dpipe_unit, Qloss_unit, Tsurf_unit. Required: Ta, Tf, ha, NPS, Tmax, kins. The full parameter table on this page comes from the server's own tool schema.
Register the EngScript Engineering MCP server in PolicyLayer and add a rule for PIPEINSUL: 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 EngScript Engineering MCP. Nothing to install.
PIPEINSUL is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the PIPEINSUL 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 PIPEINSUL. 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.
PIPEINSUL is provided by the EngScript Engineering MCP server (https://engscript.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EngScript Engineering, and thousands of servers like it.
This server
Across the catalogue