Get SimulationControl: zone/system sizing, run for sizing/weather periods, timestep.
AI agents call get_simulation_control to retrieve information from Openstudio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries simulation control parameters from an OpenStudio energy model. It has no side effects—it does not create, modify, delete, execute code, or trigger simulations. It is a read-only information retrieval function, placing it in the Read category with low severity.
From the tool's definition Tool name begins with 'get_' and description indicates retrieval of simulation control settings (zone/system sizing, run periods, timestep) with no mention of modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_simulation_control 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 get_simulation_control:
{
"version": "1",
"default": "deny",
"tools": {
"get_simulation_control": {}
}
}get_simulation_control is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get SimulationControl: zone/system sizing, run for sizing/weather periods, timestep. It is categorised as a Read tool in the Openstudio MCP Server, which means it retrieves data without modifying state.
Register the Openstudio MCP server in PolicyLayer and add a rule for get_simulation_control: 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.
get_simulation_control is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_simulation_control 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 get_simulation_control. 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.
get_simulation_control 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.