Add existing coil or heat exchanger to a plant loop's demand side.
AI agents use add_demand_component 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 creates or modifies a building energy simulation model by adding a component to a plant loop. This is a reversible change (components can be removed or modified later), making it a Write operation rather than Execute or Destructive.
From the tool's definition Tool name 'add_demand_component' and description 'Add existing coil or heat exchanger to a plant loop's demand side' indicate creation/modification of building energy model configuration.
Documented attack patterns abuse exactly the kind of access add_demand_component 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 add_demand_component:
{
"version": "1",
"default": "deny",
"tools": {
"add_demand_component": {
"limits": [
{
"counter": "add_demand_component_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_demand_component 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.
Add existing coil or heat exchanger to a plant loop's demand side. 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 add_demand_component: 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.
add_demand_component 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 add_demand_component 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 add_demand_component. 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.
add_demand_component 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.