AI agents use replace_window_constructions 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 data (window construction properties in a building model) in a reversible manner. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial).
From the tool's definition Tool name 'replace_window_constructions' indicates modification of building model properties. Server description confirms the MCP enables 'creation, querying, and modification of models.' The tool modifies existing construction definitions in an OpenStudio…
Documented attack patterns abuse exactly the kind of access replace_window_constructions 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 replace_window_constructions:
{
"version": "1",
"default": "deny",
"tools": {
"replace_window_constructions": {
"limits": [
{
"counter": "replace_window_constructions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}replace_window_constructions 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.
replace_window_constructions. 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 replace_window_constructions: 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.
replace_window_constructions 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 replace_window_constructions 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 replace_window_constructions. 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.
replace_window_constructions 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.