device_delete

Delete a device directory (cookies, profile, history). Needs confirm:true

SERVER0click Insta SOURCEakufikri/0click-insta

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0click-insta/device-delete.md

WHAT IT DOES

What device_delete does on 0click Insta

AI agents call device_delete to permanently remove resources in 0click Insta, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why device_delete is rated Critical

An AI agent that decides to call device_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 0click Insta is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs device_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 0click Insta, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For device_delete, this is the rule to start with:

device_delete Hidden

device_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "device_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 0click Insta, apply this rule, and every device_delete call is checked against it from then on.

FAQ

Questions about device_delete

What does the device_delete tool do? +

Delete a device directory (cookies, profile, history). Needs confirm:true. It is categorised as a Destructive tool in the 0click Insta MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on device_delete? +

Register the 0click Insta MCP server in PolicyLayer and add a rule for device_delete: 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 0click Insta. Nothing to install.

What risk level is device_delete? +

device_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit device_delete? +

Yes. Add a rate_limit block to the device_delete 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.

How do I block device_delete completely? +

Set action: deny in the PolicyLayer policy for device_delete. 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.

What MCP server provides device_delete? +

device_delete is provided by the 0click Insta MCP server (akufikri/0click-insta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0click Insta, and thousands of servers like it.

This server

All 44 0click Insta tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →