Delete an instance from the DataModel. This is undoable via Ctrl+Z in Studio. Args: - path (string): Path to the instance to delete Returns: Confirmation message.
AI agents call delete_object to permanently remove resources in Melo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes instances from Roblox Studio's DataModel. While the description notes undo capability in Studio, an AI agent executing this tool causes irreversible data loss in the current context—the agent cannot rely on manual Ctrl+Z intervention. This meets the definition of Destructive (irreversibly deletes data, or actions that cannot be undone).
From the tool's definition Tool name is 'delete_object' and description states 'Delete an instance from the DataModel.' The parameter is 'path' to the instance to delete, and the return is a confirmation message.
Attacks that exploit this kind of access
Delete an instance from the DataModel. This is undoable via Ctrl+Z in Studio. Args: - path (string): Path to the instance to delete Returns: Confirmation message. It is categorised as a Destructive tool in the Melo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Melo 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 Melo. 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 Melo MCP server (yannyhl/linkedsword-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →