Sandbox Kit Permission Inspector

Paste a Docker Sandbox Kit descriptor and see, in plain words, exactly what access that Kit asks for before you run it.

Descriptors are parsed locally in your browser only and never uploaded to any server. Nothing you paste leaves this page.

Honest limit: Sandbox Kit v3 is Early Access and the schema is evolving, so validation here is best-effort against the known v3 shape, not a conformance guarantee. Always check the official specification and your runtime before you trust a Kit.

Paste the descriptor JSON (media type vnd.docker.sandbox.kit.descriptor, v3), or upload the descriptor file. The inspector reads capabilities such as network-policy, credential, volume, host-mount, lifecycle, git-identity, ssh-agent, and agent skills.

How to read a descriptor

A v3 Kit is an ordinary OCI image with one descriptor that lists what the agent asks for. The Kit grants itself nothing. The runtime approves or refuses each request, and a required request that cannot be met stops the launch. Network deny rules beat allow rules, so a Kit can allow one host and still block a dangerous path on it. Credentials are the sharpest part: a conforming runtime injects the real secret for a named domain while only a placeholder value exists inside the sandbox, so the agent itself should never see your real secret in plain text.

Frequently Asked Questions

A Sandbox Kit packages an AI agent workload together with a typed list of the permissions it requests, such as network hosts, credentials, and volumes. The list travels with the image, so it can be reviewed, versioned, and signed like any other image content.
It means the v3 specification is still being shaped and details can change. This inspector checks your descriptor against the known v3 shape on a best-effort basis. It is not a conformance guarantee, and an unknown field may simply be a newer part of the spec, not an error.
The score adds up risky requests found in the descriptor, such as broad host mounts, credentials, and commands that download and run code. A low score does not prove a Kit is safe, and a high score does not prove it is malicious. It tells you where to look first, nothing more.
No. Descriptors are parsed locally in your browser only and are never uploaded to any server. You can inspect a private Kit without sending it anywhere.
A conforming runtime refuses the launch. That is by design: a Kit cannot quietly run with less access than it asked for when a request is marked required. Optional requests, or an optional group, can be skipped instead.
Deny rules take precedence over allow rules. A Kit can allow a host for normal use while denying a sensitive path or method on that same host, and the deny wins.

More tools

Was this tool helpful?

Comments

Loading comments...

Check Out Other Popular Tools