LMTD
Calculate LMTD of heat exchanger
This record as markdown: /tools/com-engscript-mcp/lmtd.md
What LMTD does on EngScript Engineering MCP
AI agents call LMTD as a supporting operation in EngScript Engineering MCP workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
Tci | object | Yes | Cold inlet temperature |
Tco | object | Yes | Cold outlet temperature |
Thi | object | Yes | Hot inlet temperature |
Tho | object | Yes | Hot outlet temperature |
LMTD_unit | string | — | Output LMTD unit |
Parameters from the server's own tool schema.
Why LMTD is rated Low
Without any rule in front of it, every call an agent makes to LMTD happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs LMTD 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 LMTD, this is the rule to start with:
LMTD 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 LMTD call is checked against it from then on.
Questions about LMTD
Calculate LMTD of heat exchanger. It is categorised as a Other tool in the EngScript Engineering MCP MCP Server, which means it performs auxiliary operations.
LMTD accepts 5 parameters: Tci, Tco, Thi, Tho, LMTD_unit. Required: Tci, Tco, Thi, Tho. 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 LMTD: 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.
LMTD 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 LMTD 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 LMTD. 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.
LMTD 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