Manage AI Permissions and Tokens

The MaskPilot local MCP tool list is defined by the installed client version. A successful connection does not mean every listed tool can run: each call still checks sign-in state, team permissions, and access to the target resource.

Let the owner configure access

The team owner decides whether a member may use AI automation and separately manages profile assignments and other feature permissions. The target profile must be visible to the member, and the required action must be allowed before a tool call can succeed.

Match the tool list to the client version

Retrieve the tool list again after the client version changes. Switching accounts or member permissions does not filter the list, but it can change whether a call is allowed. Do not guess a tool name from an old session or example. For an unknown-tool response, compare the request with the live list first.

Store the bearer token safely

• Configure the token only where the local caller needs it.
• Do not place it in a source repository, public document, screenshot, or chat history.
• Do not print complete authorization headers while troubleshooting.
• After the token changes, update the caller and restart the affected process.

Close access you no longer need

Local MCP depends on a running, signed-in MaskPilot client. Disable MCP when automation is not in use. When a member’s role changes, the owner should remove AI permission or profile assignment. If a token is exposed, replace it instead of only deleting one copy of the log.