[BUG][RBAC]: Getting 403 when adding MCP server or virtual server from team #2883
Description
🐞 Bug Summary
User access the MCP context forge UI from ICA Agentic app studio. User tries to add a new MCP or tried to create a new virtual server. The system responds with 403. Same with other crud operation like delete
🧩 Affected Component
Select the area of the project impacted:
-
mcpgateway- API -
mcpgateway- UI (admin panel) -
mcpgateway.wrapper- stdio wrapper - Federation or Transports
- CLI, Makefiles, or shell scripts
- Container setup (Docker/Podman/Compose)
- Other (explain below)
🔁 Steps to Reproduce
- Launch ICA Agentic App Studio (staging instance) and access MCP context forge.
- Select MCP Server > Add new mcp server details > Click Save.
- This gives a 403 error
- Select Virtual Server > provide details and add a new virtual server > Click Save
- This gives a 403 error
🤔 Expected Behavior
Should not return 403, instead save the MCP server or virtual server
📓 Logs / Error Output
Paste any relevant stack traces or logs here.
🧠 Environment Info
You can retrieve most of this from the /version endpoint.
1.0.0.beta2 of context forge
| Key | Value |
|---|---|
| Version or commit | e.g. v0.9.0 or main@a1b2c3d |
| Runtime | e.g. Python 3.11, Gunicorn |
| Platform / OS | e.g. Ubuntu 22.04, macOS |
| Container | e.g. Docker, Podman, none |
🧩 Additional Context (optional)
Add any configuration details, flags, or related issues.