AI agents call delete_object to permanently remove resources in Openstudio — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'delete_object' strongly suggests permanent removal of model components. In the context of OpenStudio building simulations, deleting objects cannot be undone without reloading or manual recreation. Although the description is empty (lowering confidence slightly), the name alone is unambiguous. This is categorized as Destructive rather than Write because deletion is irreversible.
From the tool's definition Tool name is 'delete_object' with no description provided. The verb 'delete' indicates irreversible removal of data from the OpenStudio energy model.
Documented attack patterns abuse exactly the kind of access delete_object 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 delete_object:
{
"version": "1",
"default": "deny",
"hide": [
"delete_object"
]
}delete_object disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_object. It is categorised as a Destructive tool in the Openstudio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openstudio MCP server in PolicyLayer and add a rule for delete_object: 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.
delete_object is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_object 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 delete_object. 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.
delete_object 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.