Skip to content

Permission Management & Safe Usage ​

MBAgent is an AI that truly can take action — it operates your files, executes commands, and operates Mbbrowser accounts. Precisely because of this, permission management and safe usage are critical.


1. MBAgent Permission Layers ​

MBAgent's permission system is divided into 5 layers:

Layer 5:Mbbrowser Client ControlV2 protocol-level restriction← Mbbrowser's own security policy
Layer 4:User permission mode (Ask / Auto / Plan)← MBAgent Settings
Layer 3:Tool approval (each tool can be set individually)← Tool-level approval
Layer 2:File sandbox (limited to working directory)← Workspace isolation
Layer 1:Operating system permissions← Your computer's account permissions

2. Permission Modes: Ask / Auto / Plan ​

Each high-risk operation pops up for your confirmation.

Target audience:

  • ✅ Newbie users
  • ✅ Scenarios involving important data / accounts
  • ✅ When unsure what AI will do

Operation flow:

AI: I want to save the file to ~/reports.xlsx
MBAgent: popup
  [Title] Write file
  [Content] AI wants to write to ~/reports.xlsx. Allow?
  [Buttons] Allow / Deny / Allow and remember

2. Auto Mode ​

Common operations auto-execute, only very few popups.

Target audience:

  • ✅ Advanced users familiar with MBAgent
  • ✅ Repetitive tasks (let AI run itself to completion)
  • ✅ Sandbox environment (no fear of AI breaking things)

Auto-executed operations:

  • Read files
  • Search web
  • Call read-only API

Still popups operations:

  • Write files
  • Execute shell commands
  • Operate Mbbrowser accounts

3. Plan Mode ​

AI first submits a plan, each step needs your approval.

Target audience:

  • ✅ Complex multi-step tasks
  • ✅ Want to understand AI's thinking
  • ✅ Don't want to be interrupted by frequent popups

Operation flow:

AI: I plan to execute the following plan:
  1. Open 10 store environments
  2. Collect order data
  3. Write to Excel
  4. Close environments
  
Please approve:
  [Approve] [Cancel] [Modify Plan]

Switch Mode ​

  1. Go to "Settings → Permissions"
  2. Select mode
  3. Save

3. Tool Approval ​

Each AI tool can have its own approval policy.

Default Approval Policy ​

ToolAsk ModeAuto ModePlan Mode
Read (read file)AutoAutoPlanning
Write (write file)PopupPopupPlanning
Edit (edit file)PopupPopupPlanning
Bash (execute command)PopupPopupPlanning
WebFetch (fetch page)AutoAutoPlanning
WebSearch (search)AutoAutoPlanning
Control Mbbrowser environmentPopupPopupPlanning
Form filling / submitPopupPopupPlanning

Custom Approval Policy ​

  1. Go to "Settings → Permissions → Tool Approval"
  2. Find the tool to adjust
  3. Select: Auto / Popup / Forbidden

4. File Sandbox ​

Working Directory Limit ​

All file operations in MBAgent can only be within the working directory you specified:

✓ /my-project/        ← Working directory, can read and write
✗ C:\Windows\        ← System directory, access forbidden
✗ D:\Private\        ← Outside working directory, access forbidden

Modify Working Directory ​

  1. Click the "Working Directory" button on MBAgent main UI
  2. Select new directory
  3. MBAgent reinitializes the sandbox

IMPORTANT

Confirm working directory at each startup: avoid MBAgent mistakenly operating a directory you didn't intend to let it touch.

Files Outside Sandbox ​

When you need to access files outside the working directory:

  1. Temporary: Copy files into the working directory
  2. Permanent: Modify working directory to include the target location
  3. Dangerous: Turn off sandbox in settings (not recommended)

5. Command Execution Limits ​

Default Blocked Dangerous Commands ​

MBAgent has a built-in dangerous command blacklist that blocks by default:

CategoryBlocked commands
System-levelformat, diskpart, bcdedit, reg delete
Network attacksnetsh firewall, net user /add
Deletionrm -rf /, del /f /s /q C:\
Process operationstaskkill /f /im, ps -ef | grep combined with kill
Download execcurl ... | bash, wget ... | sh

WARNING

Blacklist is a fallback, not absolute protection. Complex attack commands may bypass. It is recommended to still use Ask mode in important environments.

Custom Dangerous Commands ​

  1. Go to "Settings → Permissions → Command Blacklist"
  2. Add command patterns you want to block
  3. Save

6. API Key & Credential Management ​

Storage Location ​

Credential TypeStorage LocationEncrypted
Mbbrowser Account TokenMbbrowser local database✅
AI Provider API KeyWindows Credential Manager✅
Third-party account passwordTemporary in current session only❌ (memory)
Mbbrowser account passwordUsed at login only, not stored❌ (memory)

Credential Usage Flow ​

[1] User logs into Mbbrowser
    Mbbrowser account + password → Mbbrowser client validates
    ↓
[2] Mbbrowser client returns Token
    Token written to local database
    ↓
[3] MBAgent startup
    Reads Token from Mbbrowser client
    ↓
[4] MBAgent uses Token to connect ControlV2
    Token never passes through frontend chat content

Credential Security Recommendations ​

  • ✅ Regular rotation: Periodically change password in Mbbrowser console
  • ✅ Two-factor verification: Enable 2FA on Mbbrowser account
  • ✅ Independent accounts: AI operations use independent Mbbrowser sub-accounts
  • ✅ Revocation mechanism: Immediately revoke Token in Mbbrowser console when anomalies are found

7. AI Memory Bank Security ​

Memory Bank File Visibility ​

AI memory bank files are stored in:

%LOCALAPPDATA%\mbagent\memory\

Plain text — anyone who can access your computer can read it.

What Not to Store in Memory Bank ​

❌ Never store:

  • Passwords
  • Tokens / API Keys
  • Bank card numbers
  • ID numbers

✅ Can store:

  • Your preferences
  • Account numbers (not passwords)
  • Business rules
  • Public facts

Encrypted Backup ​

If you need to back up sensitive memories, recommended:

  1. Use 7-Zip encrypted compression
  2. Store on encrypted mobile HDD
  3. Don't upload to cloud drives

8. Security Audit & Logs ​

Operation Logs ​

MBAgent records all AI operations:

[2026-09-24 22:30:15] AI calls tool Write
  Params: {"file_path": "D:/my-project/reports.xlsx"}
  Result: Success
  Token: 1234

[2026-09-24 22:30:18] AI calls Mbbrowser ControlV2
  Params: {"action": "browser.start", "env_id": "223223"}
  Result: Success
  Duration: 3.2s

View Logs ​

  1. Go to "Settings → Run Logs"
  2. Enable "MBAgent Log"
  3. Log file location:
    %LOCALAPPDATA%\mbagent\logs\

Anomaly Detection ​

If suspicious operation is found:

  1. Immediately click "Stop Current Task" in MBAgent
  2. Revoke that environment's Token inside Mbbrowser
  3. Modify Mbbrowser account password
  4. Contact Mbbrowser customer support

9. Best Practices ​

For Individual Users ​

  1. ✅ Use Ask mode (default)
  2. ✅ Confirm before important operations
  3. ✅ Periodically check AI memory bank
  4. ✅ Don't let AI operate banking / payment sites

For Enterprise Users ​

  1. ✅ Use independent Mbbrowser sub-accounts for AI
  2. ✅ Limit AI's accessible environment range
  3. ✅ Enable Mbbrowser operation audit logs
  4. ✅ Periodically rotate AI's API Keys
  5. ✅ Provide MBAgent security training to employees

Dangerous Operation List ​

⚠️ What MBAgent should NOT do (even if it claims it can):

  • ❌ Modify system files / registry
  • ❌ Install / uninstall software
  • ❌ Delete databases
  • ❌ Operate payment / banking sites
  • ❌ Send external emails (unless explicitly allowed)
  • ❌ Publish content on social platforms

10. Emergency Handling ​

Immediately Stop AI ​

  • Method 1: Press Esc key
  • Method 2: Click the "Stop" button in the input box
  • Method 3: Close the MBAgent main window
  • Method 4: Close all environments inside Mbbrowser

AI Performed an Incorrect Operation ​

  1. Immediately stop (see above)
  2. Check AI memory bank, delete wrong memories
  3. Check operation logs, see what AI did
  4. Manually revoke AI's incorrect operation
  5. Add "operations that shouldn't be done" to the command blacklist

Suspect Account Stolen ​

  1. Immediately change password in Mbbrowser console
  2. Revoke all Tokens
  3. Check Mbbrowser account operation logs
  4. Contact Mbbrowser customer support

Next: Start Menu Tasks → Save frequently-used tasks as buttons.