device_create

Create an isolated device: own terminal-browser daemon, own cookie jar, own profile dir

SERVER0click Insta SOURCEakufikri/0click-insta

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What device_create does on 0click Insta

AI agents use device_create to create or update resources in 0click Insta, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0click Insta environment.

RISK

Why device_create is rated Medium

An AI agent can call device_create faster than any human can review: one bad instruction and it creates or modifies resources in 0click Insta by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs device_create 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_create, this is the rule to start with:

device_create Rate-limited

device_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "device_create": {
      "limits": [
        {
          "counter": "device_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_create call is checked against it from then on.

FAQ

Questions about device_create

What does the device_create tool do? +

Create an isolated device: own terminal-browser daemon, own cookie jar, own profile dir. It is categorised as a Write tool in the 0click Insta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on device_create? +

Register the 0click Insta MCP server in PolicyLayer and add a rule for device_create: 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_create? +

device_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit device_create? +

Yes. Add a rate_limit block to the device_create 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_create completely? +

Set action: deny in the PolicyLayer policy for device_create. 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_create? +

device_create 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 →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →