remove_demand_component

THE RISK

Critical Risk

Why remove_demand_component needs a policy

The tool removes a component from a building energy simulation model. Removal of components is an irreversible destructive action within the model context, as the component and its configuration would be lost. Severity is medium since it affects a simulation model rather than production infrastructure or financial systems.

From the tool's definition Remove coil or other component from a plant loop's demand side

Documented attack patterns abuse exactly the kind of access remove_demand_component gives an agent:

POLICY

How to control remove_demand_component

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 remove_demand_component:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_demand_component"
  ]
}

remove_demand_component disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Openstudio — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Openstudio tools

Destructive delete_object delete_object Destructive delete_run Delete one simulation run directory you own to free disk. Cancel the Destructive remove_all_zone_equipment Batch clear all HVAC equipment from multiple thermal zones in one call. Destructive remove_supply_equipment Remove boiler, chiller, or other equipment from a plant loop's supply side. Destructive remove_zone_equipment Remove heating or cooling equipment from a thermal zone. Destructive clean_unused_objects clean_unused_objects Destructive cleanup_runs cleanup_runs Execute cancel_run Cancel a running EnergyPlus simulation. Only works while status is

All 146 Openstudio tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Openstudio → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_demand_component

What does the remove_demand_component tool do? +

Remove coil or other component from a plant loop's demand side. It is categorised as a Destructive tool in the Openstudio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_demand_component? +

Register the Openstudio MCP server in PolicyLayer and add a rule for remove_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.

What risk level is remove_demand_component? +

remove_demand_component is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_demand_component? +

Yes. Add a rate_limit block to the remove_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.

How do I block remove_demand_component completely? +

Set action: deny in the PolicyLayer policy for remove_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.

What MCP server provides remove_demand_component? +

remove_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.

Enforce policy on every Openstudio tool call.

Start from Openstudio, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →