AI agents call clean_unused_objects 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 strongly implies irreversible deletion of unused objects from the building energy model. 'Clean' operations typically purge/remove data permanently, making this Destructive. Confidence is moderate because the description is empty, so we cannot confirm exact behavior, but the naming convention in OpenStudio contexts typically refers to removing orphaned/unused model objects which cannot be trivially undone.
From the tool's definition Tool name: 'clean_unused_objects' — 'clean' implies removal/deletion of objects; 'unused_objects' suggests permanent removal of model elements
Documented attack patterns abuse exactly the kind of access clean_unused_objects 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 clean_unused_objects:
{
"version": "1",
"default": "deny",
"hide": [
"clean_unused_objects"
]
}clean_unused_objects 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.
clean_unused_objects. 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 clean_unused_objects: 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.
clean_unused_objects 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 clean_unused_objects 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 clean_unused_objects. 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.
clean_unused_objects 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.