AI agents call apply_view_model as a supporting operation in OpenStudio MCP Server workflows.
The description is empty, so the tool's behavior cannot be determined from documentation alone. The name 'apply_view_model' suggests it may modify how the model is viewed or apply some view-related settings, which could be a Write operation, but without further evidence this is uncertain. Confidence is low due to the lack of description.
From the tool's definition Tool name is 'apply_view_model' and description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access apply_view_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 apply_view_model:
{
"version": "1",
"default": "deny",
"tools": {
"apply_view_model": {
"limits": [
{
"counter": "apply_view_model_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} apply_view_model gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
apply_view_model. It is categorised as a Other tool in the OpenStudio MCP Server MCP Server, which means it performs auxiliary operations.
Register the OpenStudio MCP Server MCP server in PolicyLayer and add a rule for apply_view_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.
apply_view_model is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the apply_view_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 apply_view_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.
apply_view_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.