Delete one simulation run directory you own to free disk. Cancel the
AI agents call delete_run 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.
This tool permanently removes a simulation run directory, which cannot be undone. Although the deletion is scoped to runs the user owns (limiting blast radius somewhat), the irreversible nature of deletion makes this Destructive rather than Write. Severity is high because losing simulation run data could disrupt workflows, though it is not Financial or directly Execute-based.
From the tool's definition Tool name is 'delete_run' with description 'Delete one simulation run directory you own to free disk.' The word 'Delete' combined with 'directory' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_run 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_run:
{
"version": "1",
"default": "deny",
"hide": [
"delete_run"
]
}delete_run 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 one simulation run directory you own to free disk. Cancel the. 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_run: 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_run 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_run 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_run. 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_run 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.