REFRIGERANT
Calculate refrigerant thermodynamic properties using CoolProp. Provide Fluid name and any 2 state variables from: T, P, rho, H, S, U. Returns all remaining properties: T, P, rho, H, S, U, Cp, Cv, viscosity, conductivity, molecular weight.
This record as markdown: /tools/com-engscript-mcp/refrigerant.md
What REFRIGERANT does on EngScript Engineering MCP
AI agents call REFRIGERANT as a supporting operation in EngScript Engineering MCP workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
H | object | — | Specific Enthalpy (INPUT if known). Units: J/kg, kJ/kg |
P | object | — | Pressure (INPUT if known). Units: Pa, kPa, MPa, bar, psi |
S | object | — | Specific Entropy (INPUT if known). Units: J/kg-K, kJ/kg-K |
T | object | — | Temperature (INPUT if known). Units: K, C, F |
U | object | — | Specific Internal Energy (INPUT if known). Units: J/kg, kJ/kg |
rho | object | — | Density (INPUT if known). Units: kg/m3 |
Fluid | object | Yes | Refrigerant name. Supported: R134a, R22, R32, R410A, R407C, R1234yf, R1234ze(E), Ammonia(=NH3), CarbonDioxide(=CO2) |
C_unit | string | — | Desired Cp output unit |
H_unit | string | — | Desired Enthalpy output unit |
L_unit | string | — | Desired Conductivity output unit |
M_unit | string | — | Desired Molecular Weight output unit |
O_unit | string | — | Desired Cv output unit |
Parameters from the server's own tool schema.
Why REFRIGERANT is rated Low
Without any rule in front of it, every call an agent makes to REFRIGERANT happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Risk signalsHigh parameter count (31 properties)
Attacks that exploit this kind of access
The rule that runs REFRIGERANT 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 REFRIGERANT, this is the rule to start with:
REFRIGERANT 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 REFRIGERANT call is checked against it from then on.
Questions about REFRIGERANT
Calculate refrigerant thermodynamic properties using CoolProp. Provide Fluid name and any 2 state variables from: T, P, rho, H, S, U. Returns all remaining properties: T, P, rho, H, S, U, Cp, Cv, viscosity, conductivity, molecular weight. It is categorised as a Other tool in the EngScript Engineering MCP MCP Server, which means it performs auxiliary operations.
REFRIGERANT accepts 12 parameters: H, P, S, T, U, rho, Fluid, C_unit, H_unit, L_unit, M_unit, O_unit. Required: Fluid. 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 REFRIGERANT: 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.
REFRIGERANT 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 REFRIGERANT 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 REFRIGERANT. 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.
REFRIGERANT 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