You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Custom MCP endpoints only check login. A user can still access or modify custom MCP settings after connector_custom permission is revoked. Testing an stdio MCP may start a host process.
Expected behavior
All custom MCP operations require connector_custom; denied requests return 403 before changing settings or starting a process.
Steps to reproduce
Use an account without connector_custom.
Call POST /api/connectors/custom-mcp/test with an stdio server.
Verify the request is denied and no process starts.
Environment
octop version: affected develop commit
Python version: 3.x
OS: Linux
Install method: source
Logs / screenshots
Attach the 403 response and relevant logs. Redact credentials.
Custom MCP GET, PUT, PATCH, and test now depend on connector_custom. A user without that permission gets 403 before the handler runs, so an stdio probe cannot start a host process.
New users still receive this permission by default. The hole was only open after an admin revoked it.
Activity
jubaoliang commentedon Nov 18, 2026
Custom MCP GET, PUT, PATCH, and test now depend on
connector_custom. A user without that permission gets 403 before the handler runs, so an stdio probe cannot start a host process.New users still receive this permission by default. The hole was only open after an admin revoked it.