AI agents use save_osm_model to create or update resources in OpenStudio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenStudio MCP Server environment.
The 'save_osm_model' tool creates or modifies OSM files by persisting changes to building geometry, HVAC systems, materials, schedules, and loads. While the description is empty (reducing confidence slightly), the tool name and server context clearly indicate a Write operation that reverses previous saves but does not irreversibly delete data.
From the tool's definition Tool named 'save_osm_model' with no description provided. Based on the name and context of the OpenStudio MCP Server (which manipulates OSM building energy model files), this tool saves/persists modifications to building energy models.
Documented attack patterns abuse exactly the kind of access save_osm_model gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenStudio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for save_osm_model:
{
"version": "1",
"default": "deny",
"tools": {
"save_osm_model": {
"limits": [
{
"counter": "save_osm_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_osm_model 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.
save_osm_model. It is categorised as a Write tool in the OpenStudio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenStudio MCP Server MCP server in PolicyLayer and add a rule for save_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 MCP Server. Nothing to install.
save_osm_model 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 save_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 save_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.
save_osm_model is provided by the OpenStudio MCP Server MCP server (roruizf/openstudio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenStudio MCP Server, 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.
20 OpenStudio MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.