AI agents use adjust_thermostat_setpoints 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 modifies model data (thermostat setpoints) within an OpenStudio building simulation context. This is a reversible change to model configuration, not code execution or data deletion. The empty description lowers confidence slightly, but the name clearly indicates parameter adjustment.
From the tool's definition Tool name 'adjust_thermostat_setpoints' indicates modification of building energy model parameters. Server context shows tools for 'creation, querying, and modification of models.' The action is reversible (setpoints can be adjusted again), placing it in…
Documented attack patterns abuse exactly the kind of access adjust_thermostat_setpoints 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 adjust_thermostat_setpoints:
{
"version": "1",
"default": "deny",
"tools": {
"adjust_thermostat_setpoints": {
"limits": [
{
"counter": "adjust_thermostat_setpoints_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}adjust_thermostat_setpoints 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.
adjust_thermostat_setpoints. 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 adjust_thermostat_setpoints: 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.
adjust_thermostat_setpoints 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 adjust_thermostat_setpoints 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 adjust_thermostat_setpoints. 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.
adjust_thermostat_setpoints 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.