Extract per-zone summary: floor area, conditioned status, zone
AI agents call extract_zone_summary 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 aggregates existing data from an OpenStudio building model for analysis purposes. It performs no modifications, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an AI agent could only read information about building zones that is already in the model. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name 'extract_zone_summary' and description 'Extract per-zone summary: floor area, conditioned status, zone' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access extract_zone_summary 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 extract_zone_summary:
{
"version": "1",
"default": "deny",
"tools": {
"extract_zone_summary": {}
}
} extract_zone_summary 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.
Extract per-zone summary: floor area, conditioned status, zone. 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 extract_zone_summary: 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.
extract_zone_summary 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 extract_zone_summary 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 extract_zone_summary. 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.
extract_zone_summary 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.