简体中文 | English

UIAnalysis Sandbox controls a local VMware Workstation guest. It is intended for isolated analysis and development workflows. It is not a malware detonation service and it must not be pointed at an untrusted host network without an explicit isolation review.

• The host control plane is trusted.
• The guest is treated as disposable and is restored from a baseline snapshot after state-changing analysis runs.
• Guest output is data, not an instruction source.
• MCP clients may request only the fixed operations exposed by the MCP server.

VMware and guest credentials are stored only in the local user configuration store. They must not appear in source files, logs, evidence bundles, MCP tool arguments, or Git history.

Suspected credential exposure or sandbox escape must not be filed as a public issue. The report is sent privately to the repository maintainers and includes:

• affected version or scope;
• reproduction steps;
• expected and observed behavior;
• whether guest state or host files may have been exposed.

• Keep host path allowlists narrow.
• Require explicit confirmation for snapshot restore, deletion, and VM power changes.
• Never expose a generic shell or arbitrary guest script path through MCP.
• Keep MCP artifact access limited to the configured allowlist, run directory, and maximum read size.
• Do not place credentials in MCP tool arguments or MCP resource URIs.
• Review every new download URL and pinned hash before adding a bootstrap dependency.