AI agents use change_building_location 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.
Changing building location in an energy simulation model modifies model parameters that affect all downstream simulation results and analyses. This is reversible (location can be changed again) so it is Write rather than Destructive. The empty description reduces confidence slightly, but the tool name and server context clearly indicate model modification capability.
From the tool's definition Tool name 'change_building_location' indicates modification of building model parameters. Context shows this is part of an OpenStudio energy simulation server that enables 'creation, querying, and modification of models.' The verb 'change' indicates data…
Documented attack patterns abuse exactly the kind of access change_building_location 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 change_building_location:
{
"version": "1",
"default": "deny",
"tools": {
"change_building_location": {
"limits": [
{
"counter": "change_building_location_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}change_building_location 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.
change_building_location. 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 change_building_location: 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.
change_building_location 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 change_building_location 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 change_building_location. 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.
change_building_location 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.