All Secrets must be configured before enabling a tile.

[slimslenderslacks]

Background

Today, the extension enforces this behavior. However, it is still possible to add a secret, enable a tile, and then remove the secret. Our application does not have a state to represent that this has happened.

When a secret is missing but a tile is enabled, the tool will not show up in clients because the MCP gateway can no longer run the tool to discover its tools. We log this in in the MCP gateway but these logs are not visible to the user.

Next Steps

If the MCP gateway can publish errors somewhere that is visible to users then we can at least warn users that an enabled tile can now longer be activated in the engine.