:bug: Post 0.5.0 MCP gateway updates leading to non-prefixed tool names

[evaline-ju]

Describe the bug

Previously with the 0.5.0 tag of MCP gateway we would see with current adapter ext-proc filter settingsDEBUG:ext-proc-PM:**** Invoking Tool Pre Invoke with payload: name='test2_hello_world' args={'tool_name': 'test2_hello_world',

On the latest (Kuadrant/mcp-gateway@92da659) MCP gateway there is some change in "default" behavior, where now the tool prefixes do not show up for the ext-proc

DEBUG:ext-proc-PM:**** Invoking Tool Pre Invoke with payload: name='hello_world' args={'tool_name': 'hello_world'

This may be due to unintentional filtering ordering and filter settings for the ext-proc here may be looked into. This is generally "INSERT_BEFORE" where MCP gateway routing has an INSERT_FIRST.

Steps To Reproduce

• Deploy the latest MCP gateway
• Try to guardrail tools based on names with vs. without the prefix

Expected Behavior

Default guardrailing post MCP gateway routing

Additional Context

No response

[evaline-ju]

The change happens by the v0.5.1 tag of MCP gateway

[evaline-ju]

Analysis:

In v0.5.1, the operator-based deployment updates moved the MCP gateway filter out of istio-system (root namespace) such as to gateway-system namespace, while the ext-proc filter here had stayed in istio-system, changing filter ordering

Options for updating ordering:

1. Move this ext-proc filter out of istio-system (target the same namespace as the MCP gateway envoy filter). Filters are alphabetical within the same namespace
2. INSERT_AFTER for the ext-proc filter here for explicit positioning
3. Priority field (e.g. spec.priority: 10) to ensure filter is applied after the MCP gateway

Since the filter configuration will likely be produced programmatically via operator at a later time and is more of an example in this repo [this can be deployed with or without the gateway], the last option (3) will be provided for simplicity. The filter itself can be configured to be in the same namespace as the MCP gateway filter (option 1) via
kubectl get envoyfilters -A -l app.kubernetes.io/managed-by=mcp-gateway-controller for the namespace with the MCP gateway filter. Also update workloadSelector.

Alternatively, the filter can also placed 'before' the MCP gateway filter. Configuration will just have to refer to tool names without prefixes.