AI agents call load_osm_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.
This tool appears to retrieve or load an OpenStudio model from storage, which is a read operation with no side effects. No data is created, modified, deleted, or executed. However, confidence is moderate due to the empty description; if the tool performs validation or triggers simulations upon loading, it could be reclassified as Execute.
From the tool's definition Tool name 'load_osm_model' indicates loading/retrieving an existing building energy model file (OSM format). The lack of description is a limitation, but 'load' typically implies reading/retrieving data without modification.
Documented attack patterns abuse exactly the kind of access load_osm_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 load_osm_model:
{
"version": "1",
"default": "deny",
"tools": {
"load_osm_model": {}
}
}load_osm_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.
load_osm_model. 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 load_osm_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.
load_osm_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 load_osm_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 load_osm_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.
load_osm_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.