// SCAN REPORT

0click Insta

44 tools. 24 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated: 6 Nov 2026

24 can modify or destroy data

20 read-only

44 tools total

Community server · catalogue entry checked 06/11/2026

How to control 0click Insta ↓

TOOL MAP

What 0click Insta exposes to your agents

Read (20) Write / Execute (18) Destructive / Financial (6)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous 0click Insta tools

Destructive · High challenge_solve Clear a wall: wait out Cloudflare/Turnstile, or solve recaptcha/hcaptcha through IG_CAPTCHA_PROVIDER Destructive · High delete_post Delete one of this account Destructive · High device_delete Delete a device directory (cookies, profile, history). Needs confirm:true Destructive · High logout Clear this device

24 of 0click Insta's 44 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control 0click Insta

PolicyLayer is an MCP gateway — it sits between your AI agents and 0click Insta, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "challenge_solve": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "captcha_click": {
    "limits": [
      {
        "counter": "captcha_click_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "captcha_state": {
    "limits": [
      {
        "counter": "captcha_state_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register 0click Insta — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON 0CLICK INSTA →

Instant setup, no code required.

FULL CATALOGUE

All 44 0click Insta tools

DESTRUCTIVE 6 tools

Destructive challenge_solve Clear a wall: wait out Cloudflare/Turnstile, or solve recaptcha/hcaptcha through IG_CAPTCHA_PROVIDER Destructive delete_post Delete one of this account Destructive device_delete Delete a device directory (cookies, profile, history). Needs confirm:true Destructive logout Clear this device Destructive unlike Remove a like (idempotent) Destructive unsave Remove a saved post (idempotent)

EXECUTE 5 tools

Execute device_start Open the device browser in a terminal pane (spawns a Tern split when running inside Tern) and apply the anti-d Execute device_stop Close the device Execute eval_page Run JavaScript in the device page (use it to repair selectors) Execute unfollow_bulk Unfollow only the accounts that do NOT follow back. Dry run unless confirm:true; limit caps the batch Execute unfollow_selected Unfollow exactly the handles you name: searches the following list, presses the row button, confirms. Dry run

WRITE 13 tools

Write captcha_click Move a human-shaped cursor path (CSR-S → curve → target) inside the reCAPTCHA frame and click the checkbox Write comment Comment on a post Write device_create Create an isolated device: own terminal-browser daemon, own cookie jar, own profile dir Write dm_send Send a direct message to a username Write edit_post Rewrite the caption of an existing post Write post Publish a photo, carousel or reel from local files Write proxy_set Route this device Write register Create an Instagram account through the web signup form (dry run unless submit:true) Write register_verify Finish a signup with the confirmation code Instagram sent Write save Save (bookmark) a post (idempotent) Write stealth_apply Reinstall the anti-detection profile (webdriver flag, UA, plugins, WebGL, locale) on every page target Write story_upload Upload a story when Instagram desktop exposes it (otherwise Unsupported, never a fake success)

READ 20 tools

Read captcha_state reCAPTCHA Enterprise widget state of the device page (checkbox, image challenge, sitekey), read from Instagram Read challenge_probe_text Raw text of the current page (debug helper for challenges) Read challenge_status Detect Cloudflare / captcha / Instagram checkpoint on the device page Read device_list List devices with their live browser key, handle and pane state Read dm_list List direct-message threads Read feed Read post links from the home feed Read follow Follow a username (idempotent) Read follow_status Authoritative per-account check: does this handle follow you back (followed_by) and do you follow it Read followers_list Read the accounts following this device: scroll the dialog, or filter it with search Read following_list Read the accounts this device follows: scroll the dialog, or filter it with search Read inspect_screens Walk every mapped screen on any logged-in device and report which selectors are still alive (reusable across a Read like Like a post (idempotent) Read notifications Read the notifications panel Read page_reload Reload the device page Read pane_command The exact shell command that starts this device Read profile Read a profile: bio, counts, recent post links Read status Session, handle, page and live challenge state for a device Read story_view Open a user Read ui_guide Selector map for every Instagram screen: static guide (verified or not) plus the live controls on the device Read unfollow Unfollow a username (idempotent)

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about 0click Insta

Can an AI agent delete data through the 0click Insta MCP server? +

Yes. The 0click Insta server exposes 6 destructive tools including challenge_solve, delete_post, device_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through 0click Insta? +

The 0click Insta server has 13 write tools including captcha_click, comment, device_create. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach 0click Insta.

How many tools does the 0click Insta MCP server expose? +

44 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 24 can modify, create, or delete data.

How do I enforce a policy on 0click Insta? +

Register the 0click Insta MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every 0click Insta tool call.

Deterministic rules across all 44 0click Insta tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON 0CLICK INSTA →

Instant setup, no code required.

44 0click Insta tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from 0click Insta's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →