Get detailed air loop info: components, outdoor air system, sizing, supply temperature.
AI agents call get_air_loop_details to retrieve information from Openstudio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries air loop configuration details from an existing OpenStudio model. It performs no side effects, does not create or modify data, does not execute simulations, and does not delete anything. The verb 'get' and the read-only nature of information retrieval (components, settings, parameters) clearly places this in the Read category with low risk.
From the tool's definition Tool name 'get_air_loop_details' and description 'Get detailed air loop info: components, outdoor air system, sizing, supply temperature' indicates retrieval of existing model data with no modification or execution of simulations.
Documented attack patterns abuse exactly the kind of access get_air_loop_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openstudio, and nothing reaches the server without passing your rules. This is the rule we recommend for get_air_loop_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_air_loop_details": {}
}
} get_air_loop_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed air loop info: components, outdoor air system, sizing, supply temperature. It is categorised as a Read tool in the Openstudio MCP Server, which means it retrieves data without modifying state.
Register the Openstudio MCP server in PolicyLayer and add a rule for get_air_loop_details: 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 Openstudio. Nothing to install.
get_air_loop_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_air_loop_details 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 get_air_loop_details. 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.
get_air_loop_details is provided by the Openstudio MCP server (natlabrockies/openstudio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openstudio, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
146 Openstudio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.