AI agents use create_typical_building 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.
The tool creates a new building model artifact within the OpenStudio energy simulation system, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary commands (not Execute), or move money (not Financial). The blast radius is medium because an incorrectly created model could propagate through dependent simulations and analyses, but can be corrected or deleted.
From the tool's definition Tool name 'create_typical_building' indicates creation of a building model. The server description states it enables 'creation, querying, and modification of models'. No description provided for this specific tool.
Documented attack patterns abuse exactly the kind of access create_typical_building 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 create_typical_building:
{
"version": "1",
"default": "deny",
"tools": {
"create_typical_building": {
"limits": [
{
"counter": "create_typical_building_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_typical_building 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.
create_typical_building. 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 create_typical_building: 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.
create_typical_building 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 create_typical_building 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 create_typical_building. 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.
create_typical_building 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.