Rustunnel

Expose local services via secure tunnels using rustunnel MCP server. Create public URLs for local HTTP/TCP services for testing, webhooks, and deployment.

This skill appears to do what it says: manage rustunnel tunnels by reading a per-user config file that contains an auth token. Before installing/use: (1) only provide a token you trust and consider using a short-lived token if available; (2) verify the rustunnel server address (edge.rustunnel.com) and any install URL you follow come from the official project; (3) be aware that exposing local TCP services (databases, etc.) to the public is a security risk — restrict what you expose and close tunnels when done; (4) the agent will read ~/.rustunnel/config.yml and reuse the token without prompting, so check file contents and permissions (chmod 600) and delete the file if you want the agent to prompt each time.

Type: OpenClaw Skill Name: rustunnel Version: 1.3.1 The rustunnel skill provides a legitimate interface for managing local network tunnels via an MCP server. It includes instructions for the agent to manage its own configuration file (~/.rustunnel/config.yml) and use specific tools for creating and closing tunnels. The behavior is well-documented, aligned with the stated purpose, and lacks any indicators of malicious intent or unauthorized data access.