Shift schedule profile times forward or backward by hours (24hr wrap).
AI agents use shift_schedule_time 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 schedule data within an OpenStudio/EnergyPlus model by adjusting time values. It is a Write operation because it creates or modifies data reversibly. Severity is medium because incorrect schedule shifts could degrade simulation accuracy and lead to poor building design decisions, but the effect is confined to the model and easily corrected.
From the tool's definition Tool description states it "Shift schedule profile times forward or backward" — this modifies existing schedule data in the energy simulation model.
Documented attack patterns abuse exactly the kind of access shift_schedule_time 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 shift_schedule_time:
{
"version": "1",
"default": "deny",
"tools": {
"shift_schedule_time": {
"limits": [
{
"counter": "shift_schedule_time_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}shift_schedule_time 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.
Shift schedule profile times forward or backward by hours (24hr wrap). 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 shift_schedule_time: 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.
shift_schedule_time 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 shift_schedule_time 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 shift_schedule_time. 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.
shift_schedule_time 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.