Test tool matching with conditions

[evaline-ju]

Test scenario

Tool matching should work leveraging the existing plugin manager capabilities - this should likely be tested after #29 to ensure the expected functionality is ported over

Example config

# PII detection ONLY for test2_hello_world
  - name: "PIIDetection"
    kind: "plugins.examples.nemocheck.plugin.NemoCheck"
    hooks: ["tool_post_invoke"]
    mode: "enforce"
    priority: 150
    conditions:
      - tools: ["test2_hello_world"]  # Scope to particular tools
        server_ids: []
        tenant_ids: []
    config:
      checkserver_url: "http://nemo-guardrails-service:8000/v1/guardrail/checks"
      nemo_config_id: "pii-detection"

Proposed Testing

In an cluster where multiple tools are available to the gateway, test that the plugin functionalities (at least individual Nemo rails) can be scoped to particular tools

Want to contribute?

• I would like to work on this issue.

[mvle]

The tool_pre_invoke hook works but the post_invoke hook does not. This is due to cpex's condition code matches on tool name in the MCP payload. The MCP request has the tool name in the payload whereas the MCP request body does not. The cpex payload has a field for name but we have replaceme value in there.

We will need a way to associate tool name to the MCP response message.