PIPEAIR
Calculate compressed air pipe sizing: pipe diameter, velocity, pressure drop
This record as markdown: /tools/com-engscript-mcp/pipeair.md
What PIPEAIR does on EngScript Engineering MCP
AI agents call PIPEAIR to permanently remove resources in EngScript Engineering MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
L | object | Yes | Pipe length |
M | object | Yes | Compressed air mass flow rate |
P | object | Yes | Compressed air pressure |
T | object | Yes | Compressed air temperature |
D_unit | string | — | Output pipe diameter unit |
u_unit | string | — | Output velocity unit |
dP_unit | string | — | Output pressure drop unit |
rho_unit | string | — | Output density unit |
Parameters from the server's own tool schema.
Why PIPEAIR is rated Critical
An AI agent that decides to call PIPEAIR doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from EngScript Engineering MCP is gone. There is no undo for destructive operations.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs PIPEAIR 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 PIPEAIR, this is the rule to start with:
PIPEAIR is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EngScript Engineering MCP, apply this rule, and every PIPEAIR call is checked against it from then on.
Questions about PIPEAIR
Calculate compressed air pipe sizing: pipe diameter, velocity, pressure drop. It is categorised as a Destructive tool in the EngScript Engineering MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
PIPEAIR accepts 8 parameters: L, M, P, T, D_unit, u_unit, dP_unit, rho_unit. Required: L, M, P, T. 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 PIPEAIR: 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.
PIPEAIR is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the PIPEAIR 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 PIPEAIR. 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.
PIPEAIR 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.
Across the catalogue