destroy-instance
WRITES LIVE GAME STATE. Resolve a Luau expression to an Instance and permanently remove it from the game via
This record as markdown: /tools/executor-mcp-roblox/destroy-instance.md
What destroy-instance does on Executor Mcp Roblox
AI agents call destroy-instance to permanently remove resources in Executor Mcp Roblox, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why destroy-instance is rated Critical
An AI agent that decides to call destroy-instance doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Executor Mcp Roblox is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs destroy-instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Executor Mcp Roblox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For destroy-instance, this is the rule to start with:
destroy-instance is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Executor Mcp Roblox, apply this rule, and every destroy-instance call is checked against it from then on.
Questions about destroy-instance
WRITES LIVE GAME STATE. Resolve a Luau expression to an Instance and permanently remove it from the game via. It is categorised as a Destructive tool in the Executor Mcp Roblox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Executor Mcp Roblox MCP server in PolicyLayer and add a rule for destroy-instance: 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 Executor Mcp Roblox. Nothing to install.
destroy-instance 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 destroy-instance 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 destroy-instance. 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.
destroy-instance is provided by the Executor Mcp Roblox MCP server (okenjioxx/executor-mcp-roblox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Executor Mcp Roblox, and thousands of servers like it.
Across the catalogue