Browser-local execution surface scanner

Source-first policy compiler.

Load redacted tool material, inspect the detected surface, then edit fail-closed policy and export local HELM artifacts. Verify receipt stays available as a peer mode.

01 Source

Paste, upload, or load a sample.

02 Surface

Review detected action categories.

03 Policy

Edit fail-closed decisions.

04 Export

Download local artifacts.

Boundary instrument Surface before policy.

Execution surface desk

Policy compiler

Browser-only. Raw source stays local. Handoff and telemetry are derived-only.

Sourcesample-mcp.json · 685 chars
Surfacenot compiled
Policylocked
Export2 warnings

Start with Source. Policy controls stay locked until a surface is detected.

Browser-local source

Load the execution surface first

Paste redacted MCP configs, tool manifests, GitHub scopes, or sample logs. Raw material stays in this browser.

Current source
sample-mcp.json · 685 chars
Type
MCP config
Paste or edit source
Load sample surfaces

Telemetry and review handoff use derived counts only. Raw pasted or uploaded text is never attached.

Verification remains a peer mode

Receipts are checked after the policy path is clear.

Use the Verify receipt tab to inspect EvidencePack hashes offline without changing scanner behavior or uploading source material.

Receipt artifact terms
EvidencePack
A small bundle of records used to verify one event or review path.

Route-local notes

How the local compiler boundary works.

What the compiler reads

The scanner accepts redacted MCP configs, tool manifests, GitHub scopes, and sample logs. It classifies likely side effects by category, confidence, and sanitized evidence snippets. The raw source remains in the browser and is not attached to telemetry or contact handoff.

How fail-closed defaults work

Read-only actions can move to Allow. Consequential writes move to Escalate or Deny with receipts and owner approval. Unknown custom MCP tools stay denied until a human maps the action, because absence of a known policy is treated as no authority to execute.

What leaves the browser

Exports are generated locally as Markdown, JSON, MCP overlay, and HELM kernel policy pack files. The review handoff stores only derived summaries: source type, category counts, decision counts, warning state, and custom MCP count. Pasted or uploaded source text does not leave the page.