Constant halts using MCP file/directory reads/writes/searches per this:

BoltAI2's MCP file tools are thin wrappers around POSIX file APIs. They're designed for simplicity, not scale. The serializer bottleneck (JSON validation before payload size check) is architectural—it affects ANY tool in this MCP server that uses JSON parameter arrays.

The serializer limit is a BoltAI2 server constraint, not a file-tool defect. Even if you swapped the underlying tool, you'd hit the same JSON validation ceiling on the MCP protocol layer.

Better Strategy Than Tool Swapping:

Instead of replacing BoltAI2's tools, adopt a hybrid workflow:

1. For reads >100 kB: Use ripgrep-based search tools (no size limit on results).

2. For writes >1,500 chars: Pre-split into chunks BEFORE calling edit_file (we're already doing this).

3. For bulk file ops: Use the mcp__directory_tree_17ba7w to get the structure first, then target individual small edits.

4. For escape-sensitive paths with spaces: NEVER use bash; always use the file tool wrappers.