Security center

Security scans, containment, agent safety

Scan installed apps, monitor defenses, remediate findings, and set agent safety and sandbox policy — for a machine that runs autonomous AI.

Inside VIMS Desktop · macOS · Windows · Linux · ChromeOS · Free

Sandbox policyokCredential scanokTool approvalsokAudit logok

What it does

Security Center exists because VIMS runs agents that act. It scans apps and skills, watches for risky behavior, enforces sandbox and tool-approval policy per agent, and gives you an audit trail of what was allowed.

01
App and skill scanningCheck installed code before agents use it.
02
Defense monitoringRuntime signals and containment controls.
03
Agent safety policyPer-instance sandbox, tool, and network rules.
04
ApprovalsHuman-in-the-loop for consequential actions.
05
Credential awarenessSee which keys and tokens each agent can reach.
06
AuditHistory of approvals, denials, and remediations.

How it works

  1. Review the current posture
  2. Adjust a policy or remediate a finding
  3. Verify in the audit log

FAQ

Are agents sandboxed by default?

Yes. New instances start with a restrictive policy; you loosen it deliberately.

How does VIMS Security connect to the rest of VIMS?

It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.

Related

Security scans, containment, agent safety

Security Center exists because VIMS runs agents that act. It scans apps and skills, watches for risky behavior, enforces sandbox and tool-approval policy per agent, and gives you an audit trail of what was allowed.