HEXRF
Heat exchanger fouling resistance back-calculation from shell/tube-side operating conditions.
This record as markdown: /tools/com-engscript-mcp/hexrf.md
What HEXRF does on EngScript Engineering MCP
AI agents call HEXRF as a supporting operation in EngScript Engineering MCP workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
F | object | Yes | Correction factor (dimensionless) |
A_hex | object | Yes | Total heat transfer area |
k_hex | object | Yes | Tube wall thermal conductivity |
D_shll | object | Yes | Shell inside diameter |
D_tube | object | Yes | Tube outside diameter |
D_wall | object | Yes | Tube wall thickness |
L_tube | object | Yes | Tube length |
N_tube | object | Yes | Number of tubes |
P_tube | object | Yes | Tube pitch |
Q_unit | string | — | Output heat duty unit |
R_shll | object | Yes | Shell-side fouling resistance |
R_tube | object | Yes | Tube-side fouling resistance |
Parameters from the server's own tool schema.
Why HEXRF is rated Low
Without any rule in front of it, every call an agent makes to HEXRF happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Risk signalsHigh parameter count (105 properties)
Attacks that exploit this kind of access
The rule that runs HEXRF 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 HEXRF, this is the rule to start with:
HEXRF 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 HEXRF call is checked against it from then on.
Questions about HEXRF
Heat exchanger fouling resistance back-calculation from shell/tube-side operating conditions. It is categorised as a Other tool in the EngScript Engineering MCP MCP Server, which means it performs auxiliary operations.
HEXRF accepts 12 parameters: F, A_hex, k_hex, D_shll, D_tube, D_wall, L_tube, N_tube, P_tube, Q_unit, R_shll, R_tube. Required: F, A_hex, k_hex, D_shll, D_tube, D_wall, L_tube, N_tube, P_tube, R_shll, R_tube. 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 HEXRF: 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.
HEXRF 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 HEXRF 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 HEXRF. 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.
HEXRF 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