Pre-simulation validation: weather file, design days, HVAC, constructions.
AI agents call validate_model 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.
Validation tools inspect and report on data state without modifying, deleting, or executing external operations. This is a diagnostic/quality-check function typical of Read category tools. No data is created, modified, deleted, or financial impact occurs. The blast radius of misuse is minimal—an agent could be given incorrect validation results but cannot damage the model or trigger unwanted simulations.
From the tool's definition Tool performs 'pre-simulation validation' of model components (weather file, design days, HVAC, constructions). The verb 'validate' and the context of 'checking' these elements indicates a read-only inspection operation with no side effects.
Documented attack patterns abuse exactly the kind of access validate_model 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 validate_model:
{
"version": "1",
"default": "deny",
"tools": {
"validate_model": {}
}
}validate_model 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.
Pre-simulation validation: weather file, design days, HVAC, constructions. 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 validate_model: 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.
validate_model 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 validate_model 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 validate_model. 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.
validate_model 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.