Security And Data Boundaries
AlphaBase can read and modify files, run commands, access configured providers, and connect to external tools. Treat every run as a privileged workflow and use the narrowest permissions and execution boundary that fits the task.
Permissions Are Not Isolation
Permission rules decide whether a tool call is allowed, denied, or shown for approval. They do not turn a host process into a sandbox. Review Permissions together with the selected execution policy and Network settings.
For untrusted repositories or extensions, use a container or VM boundary when
available. Do not interpret allow, Full, or an approval decision as proof
that a process cannot access host files, credentials, or the network.
Untrusted Inputs And Extensions
Treat repository instructions, skills, plugins, custom tools, MCP servers, model outputs, and generated commands as untrusted inputs until reviewed. Prompt injection can change what an agent attempts. Runtime authorization and isolation must still apply to actions requested by untrusted content.
- install only reviewed and version-pinned extensions;
- keep MCP and provider credentials narrowly scoped;
- review tool arguments before consequential actions;
- do not commit secrets to rules, skills, prompts, or tool descriptions;
- use
askordenyfor tools that can destroy data, publish changes, or reach external systems.
See MCP Servers, Plugins, and Custom Tools.
Server And Sharing Boundaries
Keep local runtimes on loopback unless remote access is intentional. A remote runtime requires authentication, encrypted transport, network restrictions, and an operator-controlled gateway. Do not expose diagnostic or control endpoints to the public internet.
Treat every share link as public. Before enabling automatic sharing, verify the deployment’s retention, expiration, revocation, and deletion behavior. See Share.
Data Handling
Data sent to an external model provider, MCP server, hosted gateway, share backend, or optional learning/synchronization service follows that deployment’s configuration and the provider’s policy. Confirm what leaves the machine, where it is processed, how long it is retained, and how it can be deleted before using AlphaBase with sensitive material. See Data Handling for the main transfer paths and controls.
Reporting
Report suspected security vulnerabilities to security@alphabase.extremeharness.com. Repository collaborators may also use the private GitHub Security Advisory form. Do not publish exploit details before the maintainers have had an opportunity to triage and coordinate a fix.