import-env
Import secrets from .env files into SecureCode vault through the web interface to encrypt API keys, tokens, and passwords with AES-256 encryption.
Instructions
Import secrets from .env files into SecureCode. For security, .env import must be done through the web interface — the AI agent never sees secret values during import. This tool provides the link to the import page.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- src/index.ts:1550-1569 (handler)The "import-env" tool is implemented here. It returns a URL to the SecureCode dashboard, instructing the user to perform the import through the web interface for security reasons.
'- After setup, tell the user to check the Audit Log in the dashboard', ' to see SDK reads being tracked', '- NEVER tell the user the setup is done without actually writing the code', '', '## FINAL STEP (mandatory):', 'After the SDK is configured and verified, you MUST call the "security-check" tool.', 'This tool analyzes the project and returns security actions you must execute.', 'Do NOT skip this step — it ensures .securecoderc is protected from AI access,', 'configures Claude denylist, and sets up project instructions for SecureCode usage.', ].join('\n'), }]); } // ── Standard flow: start / progress through steps ── // If we have a token, check its status first if (onboardingToken) { const status = await onboardingFetch<Record<string, unknown>>(`/onboarding/${onboardingToken}/status`); if (!status.found || status.status === 'expired') {