Processor usage
YOUR SERVER. YOUR RULES.
Control what agents can do.
Manage MCP access, tools and project boundaries in one place.
No server connected
Enter your connection details on the left
MCP Access
Not loadedConnect to Guardian 0.30.0+ to load the server-side access policy.
No policy loaded.
Policy is saved on the VPS and shared by upgraded Guardian processes running as this SSH user. Older agents must upgrade and reconnect once. This is an MCP boundary, not isolation from root SSH or server-code access.
Projects
Explore project metadata inside the configured roots. No source is read and no project commands are executed.
Connect to Guardian 0.31.0+ on the VPS to browse projects.
Selecting or inspecting a project does not change agent permissions. Use as root prepares an Access draft; review and Apply permissions there. Explicit managed roots are shared; inherited roots may differ between agent launch environments.
Resource limits
Not loadedShared, server-enforced budgets for subsequent operations. Host protection always applies, including with Standard and Custom profiles.
Connect to Guardian 0.31.0+ to load limits.
Capsule isolation stays fixed: 128 MiB RAM, 0.5 CPU, 30 seconds, 4 KiB output. These cooperative limits do not impose a global CPU/RAM quota, cancel in-flight operations or constrain ordinary SSH. Upgrade every agent's server executable to 0.31.0+ and reconnect once.
Server overview optional · read-only · 30s refresh
Memory usage
Root filesystem
Services
systemd—
—
—
Monitoring also respects the MCP access policy.