Bug: SK runs his self-made function by ignoring the auto-invoke function config

Describe the bug
I set the toolcallbehavior of allowOnlyKernelFunctions as true, and passed the functions to the kernel
but the kernel make a functiontoolcall by himself and just invoke it.

To Reproduce
Steps to reproduce the behavior:

         List<KernelFunction<?>> functions = kernel.getPlugins().stream()
                .map(KernelPlugin::getFunctions)
                .map(Map::values)
                .flatMap(Collection::stream)
                .toList();
        FunctionResult<String> preResult = kernel
                .invokeAsync(function)
                .withToolCallBehavior(ToolCallBehavior.allowOnlyKernelFunctions(true, functions))
                .withArguments(
                        KernelFunctionArguments.builder()
                                .withInput(userInput)
                                .withVariable("metadata", metadata)
                                .build())
                .withResultType(ContextVariableTypes.getGlobalVariableTypeForClass(String.class))
                .block();    // occur exception here, for invoke a self-make function

Expected behavior
Only invoke the passed functions.

Screenshots

Maven

• Version: 3.3.9
• Dependencies: 1.4.3

Platform

• IDE: IDEA
• JDK version: 17

Additional context
Excption: com.azure.core.exception.HttpResponseException: Status code 400, "{"error":{"message":"Invalid 'messages[1].tool_calls[1].function.name': string does not match pattern. Expected a string that matches the pattern '^[a-zA-Z0-9_-]+$'.","type":"invalid_request_error","code":"invalid_value","param":"messages[1].tool_calls[1].function.name"}}"

Commencez par reproduire l’exemple Java autour de kernel.invokeAsync(function) et ToolCallBehavior.allowOnlyKernelFunctions(true, functions) avec les versions indiquées. Examinez la manière dont les fonctions transmises sont traitées avant l’envoi de l’appel d’outil ; le travail est terminé lorsque seules les fonctions du kernel fournies sont invoquées et que la requête de nom de fonction non valide signalée n’est plus générée.