Do the tools for agent nodes support dynamically specifying IP:port?

[ToWorld]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Do the tools for agent nodes support dynamically specifying IP:port?

[dosubot[bot]]

Hi @ToWorld — this is actually the same question you asked in your previous discussion, and the answer is the same for agent node tools:

No, tools in agent nodes do not support dynamically specifying the server IP:port at runtime. The server URL is fixed at parse time from the servers[0].url field in the OpenAPI schema and baked into the ApiToolBundle.server_url — it is never re-evaluated per invocation [1].

This applies regardless of whether the tool is used in a workflow tool node or an agent node, since agent nodes route API-type tools through the same ApiTool invocation path [2].

Workarounds:

1. Multiple servers entries with env tags — pre-define all possible base URLs in the schema and use the X-Request-Env header to select among them [1].
2. Reverse proxy — place a proxy with a stable address in front of your backends.
3. HTTP request via Code node — if you truly need a runtime-dynamic URL, use a Code node in a workflow to make the HTTP call directly instead of a custom tool.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[ToWorld]

Hi @ToWorld — this is actually the same question you asked in your previous discussion, and the answer is the same for agent node tools:

No, tools in agent nodes do not support dynamically specifying the server IP:port at runtime. The server URL is fixed at parse time from the servers[0].url field in the OpenAPI schema and baked into the ApiToolBundle.server_url — it is never re-evaluated per invocation [1].

This applies regardless of whether the tool is used in a workflow tool node or an agent node, since agent nodes route API-type tools through the same ApiTool invocation path [2].

Workarounds:

1. Multiple servers entries with env tags — pre-define all possible base URLs in the schema and use the X-Request-Env header to select among them [1].
2. Reverse proxy — place a proxy with a stable address in front of your backends.
3. HTTP request via Code node — if you truly need a runtime-dynamic URL, use a Code node in a workflow to make the HTTP call directly instead of a custom tool.

To reply, just mention @dosu.

Docs are dead. Just use Dosu.

Is customization possible? However, this doesn't quite fit the design of using prompts and tool lists as static prefixes.