Change the name of any model object (space, zone, HVAC component, schedule, etc.).
AI agents use rename_object 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 modifies model metadata but does not create or delete objects (Write, not Execute or Destructive). The blast radius is medium because renaming objects could break downstream references or cause confusion in simulation workflows, but the change is reversible and does not affect physical data deletion or financial/external operations.
From the tool's definition Tool explicitly performs object renaming, which modifies existing model data. The description states it can change names of various model objects (spaces, zones, HVAC components, schedules, etc.), which is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access rename_object 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 rename_object:
{
"version": "1",
"default": "deny",
"tools": {
"rename_object": {
"limits": [
{
"counter": "rename_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_object 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 the name of any model object (space, zone, HVAC component, schedule, etc.). 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 rename_object: 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.
rename_object 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 rename_object 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 rename_object. 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.
rename_object 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.