Get status of the currently loaded model.
AI agents call get_current_model_status to retrieve information from OpenStudio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an already-loaded building energy model. It performs no modifications, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an AI agent querying model status cannot cause harm beyond potentially wasting API calls or leaking non-sensitive metadata about the model structure. This is a straightforward Read operation.
From the tool's definition Tool name 'get_current_model_status' and description 'Get status of the currently loaded model' indicate a query operation that retrieves information about the current state of a loaded OSM file without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access get_current_model_status 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 get_current_model_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_model_status": {}
}
}get_current_model_status 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 status of the currently loaded model. It is categorised as a Read tool in the OpenStudio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenStudio MCP Server MCP server in PolicyLayer and add a rule for get_current_model_status: 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.
get_current_model_status 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_current_model_status 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_current_model_status. 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_current_model_status 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.