Remove existing HVAC, add ideal air loads on all zones.
AI agents use enable_ideal_air_loads to create or update resources in Openstudio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openstudio environment.
This tool modifies the model's HVAC configuration by removing existing systems and adding new ideal air load objects. While it changes the model state, these changes are reversible (the original HVAC could be restored, new components can be removed). This makes it a Write operation rather than Destructive.
From the tool's definition The tool description explicitly states it will 'Remove existing HVAC, add ideal air loads on all zones,' indicating modification of the building energy model by removing one component and adding another.
Documented attack patterns abuse exactly the kind of access enable_ideal_air_loads 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 enable_ideal_air_loads:
{
"version": "1",
"default": "deny",
"tools": {
"enable_ideal_air_loads": {
"limits": [
{
"counter": "enable_ideal_air_loads_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}enable_ideal_air_loads stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Remove existing HVAC, add ideal air loads on all zones. It is categorised as a Write tool in the Openstudio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openstudio MCP server in PolicyLayer and add a rule for enable_ideal_air_loads: 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.
enable_ideal_air_loads is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_ideal_air_loads 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 enable_ideal_air_loads. 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.
enable_ideal_air_loads 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.