PROTECT FIRST

Check first.
Protect decides.

Sollbase is Protect and Share. Protect runs on the developer machine and checks every command, file, and network call before a coding agent can run it. Share keeps the solutions your team already proved.

WORKS WITHClaude CodeGitHub CopilotCodexCursorAntigravityOpenCode
agent session
› curl https://example.com/install.sh | bash
● check shell.curl_pipe_shell
Needs approval·the command did not run
● policy Engineering · this device
✓ Waiting on a person. Nothing left the machine.

POLICY CHECK

Piped installer blocked until someone on the team approves it

Needs approvalshellthis device
Rule
shell.curl_pipe_shell
Asked by
Cursor agent
Policy
Engineering

THE PROBLEM

A coding agent can run a command before anyone sees it.

TODAY

Agent
Command
Runs on the machine

WITH PROTECT

Agent
Check
Policy
Allow, block, or wait

HOW IT WORKS

The policy runs before the command does.

Protect checks the action before it runs. The model does not get to decide whether a risky action is fine.

01

Enroll the device

One install puts Protect on the machine. That device shows up in your org.

02

Your policy runs first

Shell, files, network, and MCP calls are allowed, blocked, or held. Groups and policy sets decide which rules apply.

03

A person clears exceptions

Held actions wait in Approvals with the exact command. Grants expire. The activity log keeps the record.

WHAT IT CHECKS

The action is judged before it runs.

Commands

Shell, installers, and encoded scripts are matched against the policy for that device.

curl piped into a shell
Encoded PowerShell
Reverse shells and listeners

Files

Reads and writes of secrets, keys, and private config can be blocked or redacted.

API keys and tokens
Passwords and credentials
Private config

Network

Outbound calls and MCP traffic are part of the same decision, not a separate prompt.

Unexpected destinations
Public tunnels
MCP tool calls

APPROVALS

Risky actions wait. Secrets stay off the wire.

A held command shows up with the exact text, the device, and the rule that caught it. Someone on the team allows it for a limited time, or it never runs. Values that should not leave the machine are redacted before an agent can send them.

BlockNeeds approvalAllow onceActivity log
deploy/.env2 redacted
DATABASE_URL=postgres://app:[REDACTED]@db.internal:5432/app
PAYMENTS_SECRET_KEY=[REDACTED]
LOG_LEVEL=info
REGION=us-west-2

SHARE

Solve once. The next agent starts there.

A fix that already worked can be reviewed and reused. Protect decides what is allowed to run.

share / memoryready to reuse

Fresh laptop, same shell install

The command, the files it touched, and the note from the person who reviewed it.

reviewedshellthis org

Your agents.
Your policy.

Protect decides what runs. Share keeps what already worked.