Config delivery and forward-per-request key fields are saved for mcp apps with source non-app runner but not forwarded to core

[AnastasiiaHarkot]

EPAM AI DIAL Admin version

[FE]0.17.0-dev.48 [BE]0.17.0-dev.7

How to reproduce

1. In Admin panel, create or open an mcp application whose source is not application runner
2. Navigate to the configuration section of the application
3. Fill in the config delivery and forward-per-request key fields
4. Save the configuration
5. Check core service to verify whether the configuration was forwarded

Actual result

For mcp applications whose source is not application runner, config delivery and forward-per-request key fields are displayed and allow saving in Admin panel. However, the saved configuration is not forwarded to core, resulting in a silent data inconsistency — the values are persisted on Admin side but have no effect.

Expected result

Config delivery and forward-per-request key fields should only be available and valid for applications based on Application Runner. For mcp applications with a different source, these fields should not be present or should be non-editable, and no data related to them should be sent core.

Note:

• Config delivery and forward-per-request key are only supported for ppplication runner-based applications
• Mcp applications can only be created on top of application runner, therefore these fields must be scoped exclusively to that source type

Additional information

No response

Confidential information

• I confirm that do not share any confidential information

[KirylKurnosenka]

Linked with epam/ai-dial-core#1519