use-slicer-proxy

Manage microVM egress traffic with default-deny policy and secret injection.

3|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/slicervm/agent-skills --skill use-slicer-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-slicer-proxy
Source: https://github.com/slicervm/agent-skills/tree/main/skills/use-slicer-proxy
Command: npx skills add https://github.com/slicervm/agent-skills --skill use-slicer-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of securely managing egress traffic from Slicer microVMs, ensuring secure and controlled access to external resources.

Core Features & Use Cases

  • Egress Filtering: Block all egress traffic except that which is explicitly allowed, providing strong security for microVMs.
  • Secret Injection: Automatically inject credentials for HTTP(S) requests, preventing credentials from being stored on the VM.
  • Audit Mode: Log all denied HTTP(S) requests, allowing for security auditing and discovery of required services.
  • TCP Passthrough: Support for secure, raw TCP connections to services like SSH and Postgres.
  • Use Case: Imagine you want to ensure that a microVM can only access specific external APIs while running, and that it must use secure credentials for each request. Use this Skill to configure rules that enforce these restrictions.

Quick Start

Configure the proxy to allow HTTP(S) traffic to 'api.example.com' using the token 'proxy-token'.

Frequently Asked Questions about use-slicer-proxy

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

FAQPage Schema
How do I block all microVM egress traffic except specific APIs?

You can inject credentials for HTTP(S) requests by configuring secret management rules, ensuring secure tokens like proxy-token are automatically applied without being stored on the microVM.

How do I securely inject credentials into HTTP(S) requests from a microVM?

You can inject credentials for HTTP(S) requests by configuring secret management rules, ensuring secure tokens are automatically applied without being stored on the microVM.

Can I log denied egress requests to discover required external services?

Yes, you can enable audit mode to log all denied HTTP(S) requests, which allows for security auditing and helps discover required external services that need to be explicitly allowed.

Does the proxy support raw TCP passthrough for SSH and Postgres connections?

Yes, the proxy supports TCP passthrough to provide secure, raw TCP connections for services like SSH and Postgres within the Slicer microVM environment.

What is the best way to manage egress security for Slicer microVMs?

The best way to manage egress security is using a default-deny proxy policy combined with explicit allow rules and automated secret injection to control access to external resources.