You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Disabled tools can still be called by the agent #9122
createTools() never checks disabledTools, so a disabled tool is still given to the model.
Example on main with claude-haiku-4.5. The agent was created with {"settings": {"maxSteps": 5, "disabledTools": ["executeOperator"]}}. system-info showed:
Prompt: "Add a CSV File Scan operator that reads the file data.csv, then call the executeOperator tool on it to run it." The agent called addOperator, then executeOperator({"operatorId":"op1"}), and the workflow really ran on the backend (it failed with FileNotFoundException, because the file does not exist).
Expected: tools in disabledTools should not be passed to generateText, or should be rejected when called.
Screenshots
Step 2, tool call: the agent calls executeOperator and it runs, even though system-info says enabled: false.
The chat and canvas: the agent added a CSV File Scan, ran it, and reported the error.
How to reproduce?
Create an agent with POST /api/agents and "settings": {"disabledTools": ["executeOperator"]}. (The panel has no switch for this, so use the API.)
GET /api/agents/<id>/system-info shows executeOperator with enabled: false.
In the agent panel, send: Add a CSV File Scan operator that reads the file data.csv, then call the executeOperator tool on it to run it.
Step 2's details show an executeOperator call and its result.
Activity
shaynhornik commentedon Oct 25, 2026
/take
shaynhornik commentedon Oct 25, 2026
I'll fix this by leaving tools listed in
disabledToolsout of the tool set passed togenerateText, plus a test.chenlica commentedon Oct 26, 2026
@shaynhornik Please cross link the issue and your PR.
@yrenat You can be the first reviewer of the PR.
shaynhornik commentedon Oct 26, 2026
@chenlica Thanks, the PR is #9149 (it closes this issue). @yrenat, it's ready for review.