get_sizing_zone_properties

THE RISK

Low Risk

Why get_sizing_zone_properties needs a policy

This tool retrieves existing zone sizing configuration parameters from an OpenStudio building energy model. It performs only read operations with no side effects, data modification, code execution, or destructive actions. The blast radius of misuse is minimal — an agent could retrieve design specifications but cannot alter them or trigger simulations.

From the tool's definition Tool name includes 'get_' prefix and description explicitly states 'Read zone sizing parameters' with operations limited to retrieving 'design air flow, supply temperatures, DOAS settings' — all query operations with no modification.

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

POLICY

How to control get_sizing_zone_properties

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_sizing_zone_properties": {}
  }
}

get_sizing_zone_properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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.

CAP 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_demand_component Remove coil or other component from a plant loop's demand side. 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

All 146 Openstudio tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_sizing_zone_properties

What does the get_sizing_zone_properties tool do? +

Read zone sizing parameters: design air flow, supply temperatures, DOAS settings. It is categorised as a Read tool in the Openstudio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sizing_zone_properties? +

Register the Openstudio MCP server in PolicyLayer and add a rule for get_sizing_zone_properties: 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 get_sizing_zone_properties? +

get_sizing_zone_properties is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_sizing_zone_properties? +

Yes. Add a rate_limit block to the get_sizing_zone_properties 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 get_sizing_zone_properties completely? +

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

get_sizing_zone_properties 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 →