fix(agent): #5544 strictly enforce toolset filters for memory provide…

[MustafaKara7]

…r injection

What does this PR do?

Fixes #5544

The MemoryManager dynamically injects fact_store tools after the primary tool registry initialization. Previously, this bypassed enabled_toolsets and disabled_toolsets filters, causing massive token overhead and tool-loops for local models when platforms (e.g. Telegram) explicitly requested zero tools (telegram: []).

Added explicit validation against both self.enabled_toolsets and self.disabled_toolsets before appending memory schemas to self.tools, ensuring full compliance with user configurations.

Fixes #5544

[thundercat49]

Tested this approach on my local setup (RTX 3090, Qwen3-30B-A3B via llama.cpp) and the logic is correct — response time dropped from 42s to ~2s with telegram: [].
Minor: line 3 (if self._memory_manager and self.tools is not None:) looks like a leftover from the original code — it has no body and falls through silently. Should be removed to keep the diff clean.

[alt-glitch]

Likely duplicate of #5788 — both fix memory tool injection bypassing platform_toolsets/enabled_toolsets config.

[teknium1]

Thanks for identifying the late memory-tool injection path. The disabled-toolset part of the report remains valid on current main, but this patch needs a focused port.

Problems

• The modified inline block no longer exists: current main injects via agent/memory_manager.py:100-145, invoked from agent/agent_init.py:1419-1420 after the base list has already been filtered at agent/agent_init.py:1159-1163.
• The current helper checks only enabled toolsets at agent/memory_manager.py:112-116; it does not read disabled_toolsets, so the denylist bypass remains.
• Do not port the direct membership check verbatim: agent/memory_manager.py:91-94 resolves composite toolsets, and tests/agent/test_memory_provider.py:1363-1368 requires hermes-acp to retain provider memory tools.

Suggested changes

• Add a denylist-first memory gate in inject_memory_provider_tools(), retain the existing composite enabled-toolset resolver, and add tests for disabled-memory precedence in tests/agent/test_memory_provider.py.

Automated hermes-sweeper review.

[teknium1]

Do not carry this direct membership check into the current helper unchanged: current main supports composite toolsets through memory_provider_tools_enabled() (agent/memory_manager.py:91-94), and tests/agent/test_memory_provider.py:1363-1368 verifies that hermes-acp exposes provider memory tools. Preserve that resolver and add the disabled-toolset check separately.