[shaynhornik]

What changes were proposed in this PR?

Tools in settings.disabledTools were shown as enabled: false by system-info, but sendMessage still passed every tool to generateText, so the agent could call a disabled tool and it ran.

sendMessage now passes only the enabled tools, through a small getEnabledTools() helper. this.tools is unchanged, so getSystemInfo() still lists every tool with its enabled flag.

Any related issues, documentation, discussions?

Closes #9122

How was this PR tested?

Two new tests in texera-agent.spec.ts, both using the ai/test mock model:

• With modifyOperator disabled, the model call gets only deleteOperator and addOperator, and system info still lists modifyOperator as disabled.
• With deleteOperator disabled, a model that calls it anyway does not delete the operator.

Both fail without the change. Locally: bun test (312 pass), tsc --noEmit and prettier --check are clean.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Claude Opus 5.5). I reviewed and tested the change.

🤖 Generated with Claude Code

[github-actions]

Backport auto-label report

This fix: PR was checked against each actively-supported release branch. A release/* label nominates a backport target; the branch's release manager approving this PR is what sends the fix there. The required Backport Approvals check stays red until every label below is approved, so each manager either approves or removes their own label — which is why the labels left on a merged PR are exactly the branches it reached.

Release branch	Analysis
✅ release/v1.3	Change detected on this branch — label added; this fix is queued to backport here. @mengw15 decides: approving sends the fix here, removing this label declines it. The merge waits on one or the other. Review requested.
✅ release/v1.2	Change detected on this branch — label added; this fix is queued to backport here. @xuang7 decides: approving sends the fix here, removing this label declines it. The merge waits on one or the other. Review requested.

Auto-label run.

[github-actions]

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

• Contributors with relevant context: @roshiiiz
  You can notify them by mentioning @roshiiiz in a comment.

[github-actions]

👋 Thanks for your first contribution to Texera, @shaynhornik!

If you're looking for a good place to start, browse issues labeled starter-task; they're scoped to be approachable for newcomers.

You can drive common housekeeping yourself by commenting one of these commands on its own line:

• Issues. Comment /take to assign an open issue to yourself, or /untake to release it. You can find unclaimed work with the search filter is:issue is:open no:assignee.
• Sub-issues. To link issues into a parent/child hierarchy, comment /sub-issue #5166 #5222 on the parent to attach those children (or /unsub-issue #5166 #5222 to detach them). From a child issue, comment /parent-issue #5166 to set its parent, or /unparent-issue to clear it (the current parent is detected automatically). References may be written as #5166 or as a bare 5166; cross-repository references are not supported.
• Pull requests (author only). Comment /request-review @user to request a review from someone, or /unrequest-review @user to withdraw that request.

Each command must match exactly: /take this will not work, only /take does. For the full contribution flow, see CONTRIBUTING.md.