[Bug]: Removing the Authentication Header in Workspace does not get reflected in Gateway

Please select the area the issue is related to

AI Workspace

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Description

Hi Team,

It was observed the even when we remove the Authentication Header in Workspace it does not get reflected in gateway and it will passed to the backend. Please refer to the Steps to Reproduce below.

Best Regards,
Hasitha

Steps to Reproduce

1. Create an MCP proxy with adding a local MCP server(To check the headers easily) with an Authentication Header
2. Invoke the Proxy and see the header is passed to the backend
3. Remove the header from the Workspace and deploy
4. Invoke the proxy and still you can see the header is passing to the backend
5. Add a new header like AuthABC and deploy again
6. Invoke the Proxy and see the header is passed to the backend with new header name
7. Remove the new header from the Workspace and deploy
8. Observe the new header is passed even through it is removed from the workspace.

Severity Level of the Issue

Severity/Minor (Non-critical functionality. Can be fixed in future releases)

Environment Details (with versions)

No response

Start by reproducing the issue with a local MCP server, following the workspace-to-gateway deployment steps in the report. Trace how authentication headers are synchronized when a proxy is redeployed; done means removing a header in Workspace prevents it from reaching the backend, including after adding and then removing a replacement header.