Security
Security and the limits of agent access
Understand the customer Runner, the permissions you configure and the limits that need your attention.
Execution modes
Customer execution
Customers run agents on their own machine through the MasterMNG Runner and Claude Code. The hosted command center organizes that work.
| Mode | Who can use it | Where the provider credential lives | What MasterMNG holds |
|---|---|---|---|
| Your machine, through the MasterMNG Runner | Claude plan through Claude Code | In the provider's own CLI, signed in by you on that machine. It is never sent to MasterMNG. | A runner token stored only as a hash, the run's output (redacted on your machine and again on our server) and which CLI is installed and signed in. Never the credential. |
| Subscription sign-in in the hosted service | Not used | — | The hosted service refuses to collect, store or relay subscription sign-ins. |
In the product
Agents act within limits you can see.
Agent identity fails closed
Every agent request must carry that agent's own signed credential, issued for its run. A request without a valid one is refused — it is never treated as the owner or the board.
Decisions are enforced at the server
Governed actions are enforced where they execute, not only in the interface. An approved operation is bound to that exact operation, authorized when it runs and usable once. The waiting agent is woken once.
Handoffs cannot escalate
A handoff is a record scoped to one organization and one task. Nothing an agent writes in it can grant that agent, or the next one, additional permissions.
Your provider accounts stay yours
We never ask for provider passwords. Subscription sign-ins on your own machine stay in the provider's command-line tool and are not sent to MasterMNG. Provider accounts are never pooled across organizations.
Limitations
Scope and limitations
No hosted agent execution
Running agents on MasterMNG infrastructure is not offered to customers and has no date. Agents run on your own machine through the MasterMNG Runner.
The runner is not a sandbox
The MasterMNG Runner acts as the user who starts it. If the machine holds data agents must not reach, run it under a dedicated user or in a virtual machine. macOS and Linux only.
Tool limits are partial on your own machine
On the tool gateway, project tools and the MasterMNG runtime, the server enforces tool permissions and approvals. On a customer's machine MasterMNG sets the limits and the provider's own CLI applies them, so enforcement there is partial. Operating rules remain guidance to agents. See Governance & Attention.
Service availability
No service-level agreement, high-availability commitment or recovery objective is offered on this page.