POLICY TOOL
Enterprise policy generator
Build a managed policy.json in the browser. Nothing is uploaded. Download the file, then put it where the desktop app expects it.
Field docs live in the policy reference.
Start from a preset
Pick a baseline, then edit the JSON before shipping it.
Guardrails
guardrailsEnforced0 of 8 setLocks for the per-machine security.json — outside-workspace policy, blocked/sensitive command lists, and path permissions.
lockNot setLock every security.json key at every scope, so project, workspace, and global toggles stop having any effect and the merged config reports lockedFields covering all keys. Writes to a locked field return 409 PolicyLocked, as does reset-to-defaults while any guardrail is locked.
lockedFieldsNot setParsedSubset of security.json keys to lock (e.g. outsideWorkspace).
forceOutsideWorkspaceNot setPin the outsideWorkspace policy at every scope, so a project security.json cannot loosen it. "blocked" refuses every read or write outside the workspace; "ask" prompts for each access.
mandatorySensitivePatternsNot setGlob patterns unioned into the merged sensitivePatterns list. Users cannot remove these entries at any scope.
mandatoryBlockedCommandsNot setShell command glob patterns unioned into the merged blockedCommands list. Users cannot remove these entries at any scope.
mandatoryAskCommandsNot setParsedShell command glob patterns the agent must ask before running. Unioned with the merged askCommands list; users cannot remove these.
disableUserAllowedCommandsNot setParsedPrevent users from extending allowedCommands at any scope. The effective allowed list comes from policy and built-ins only.
mandatoryPathPermissionsNot setParsedRecord of { path: { read?, write?, bash? } }. Each level is "allowed" | "ask" | "blocked".
Deploy it
The loader checks exactly one path. Put the downloaded file there.
/etc/voidleap/policy.json/Library/Application Support/Voidleap/policy.jsonC:\ProgramData\Voidleap\policy.json- An administrator must own it
- On Linux and macOS the file must be owned by root (uid 0). On Windows it must stay under
C:\ProgramData\Voidleap\. - A broken file fails closed, not open
- A missing file means no managed policy. A file that is present but unreadable, wrongly owned, malformed, or schema-invalid is not ignored: by default the loader applies a restrictive fallback policy instead of yours, which additionally sets
plugins.disableInstall: trueandhooks.disable: true. The reason is logged and reported byGET /policy/status, which is the first thing to check when a policy looks wrong. - VOIDLEAP_POLICY_STRICT_FALLBACK turns that off
- Setting it to
0orfalserestores the old permissive behaviour. Unset, or any other value, leaves strict fallback on. It is a server environment setting, not a field in this file. Repair the policy and reload rather than leaning on the fallback. - Edits need a reload
- The policy is cached for the lifetime of the process. Restart Voidleap, or call
GET /policy/status?reload=true, which also refreshes the already-loaded runtime configurations and the agent, custom-tool, and MCP server registrations. - VOIDLEAP_POLICY_PATH overrides the path
- Testing only, and logged loudly on every load. Do not ship it to a fleet.
Trust note
Runs entirely in your browser. Nothing is uploaded. The generated file is just JSON.