starhub-kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compile_ai_sandbox_policyC | Compile zero-lateral-movement firewall / ACL policy for autonomous AI coding agents (Linux nftables, macOS pf, Tailscale ACL JSON, or Linux iptables). |
| render_quic_mesh_guardrailsC | Render deterministic Tailscale split-DNS + surgical Apple/Gmail UDP/443 QUIC ruleset for Sing-box or Mihomo (Clash Meta). |
| audit_topology_securityC | Audit a StarHub topology JSON for RFC 1918 Wi-Fi subnet collisions and exposed AI sandbox SSH/database ports. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct action and target: rendering QUIC/mesh guardrails, auditing topology security, and compiling AI sandbox policy. There is little risk of confusing one tool for another despite the shared networking/security domain.
All tool names use consistent snake_case with a leading verb and descriptive noun phrase. The pattern is predictable across render_, audit_, and compile_.
Three tools is well-scoped for a specialized network/security policy kit, with each tool covering a distinct workflow. No tool appears redundant or out of place.
The surface covers rendering guardrails, auditing topology, and compiling sandbox policy, which are the core operations implied by the kit. Minor gaps exist around validating generated outputs or applying policies, but agents can work around these.