configuring-sandbox-allowlist

Edits the tinyproxy sandbox hostname allowlist with refusal rules and rebuild verification.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill configuring-sandbox-allowlist-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configuring-sandbox-allowlist
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/configuring-sandbox-allowlist
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill configuring-sandbox-allowlist-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Sandboxed agent runners rely on a default-deny tinyproxy filter, and editing that hostname allowlist incorrectly (wildcards, IP literals, metadata hosts) silently breaks the security boundary. This Skill enforces disciplined add, remove, and audit operations on the filter file so every change stays safe and verifiable. ## Core Features & Use Cases - Guarded Add/Remove Operations: Validates POSIX-anchored regex patterns, refuses wildcards, IP literals, metadata-service hosts, and internal domains before touching docker/sandbox-proxy/filter. - Allowlist Auditing: Classifies existing entries as active, stale, or suspect using proxy logs and produces a markdown audit table without editing the file. - Verification Discipline: Surfaces the exact proxy rebuild and just doctor --full egress-test commands after every change, plus a PR description template. - Use Case: A sandboxed implement run fails because tinyproxy denied api.partner-example.com. Use this Skill to validate the hostname, add an anchored pattern to the correct filter section, and get the rebuild and egress-test commands to confirm enforcement. ## Quick Start Add api.example.com to the sandbox allowlist and show me the rebuild and verification commands.

Frequently Asked Questions about configuring-sandbox-allowlist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a hostname to a tinyproxy sandbox allowlist?▼

Validate the pattern as POSIX extended regex anchored with ^...$ and escaped dots, confirm the host resolves with getent or dig, then append it to the correct section of the filter file. Afterward rebuild the proxy image with --no-cache and run the egress test.

How to audit a proxy allowlist for unused entries?▼

Group filter entries by section, then cross-reference proxy logs from the last 30 days for per-host hit counts. Classify each entry as active, stale, or suspect, output an audit table, and remove stale hosts through separate removal operations.

Why are wildcards refused in a default-deny proxy filter?▼

Multi-label wildcards like ^.*\.example\.com$ allow subdomain takeover to bypass the gate, defeating default-deny. The safer alternative is enumerating exact subdomains, such as ^(api|cdn)\.example\.com$.

Can I add IP addresses or internal hosts to the sandbox filter?▼

No. IP literals bypass DNS-based attribution, and metadata or internal hosts like 169.254.169.254 or *.internal are credential-exfiltration vectors. These patterns are refused; network-level exceptions require a deliberate tinyproxy.conf change with team-lead review.

Why must the proxy be rebuilt after editing the filter file?▼

Tinyproxy reads the filter only at startup, so the running container keeps the old rules. Rebuilding with --no-cache prevents Docker from serving a cached layer with the stale filter, and restarting the container loads the new rules.