File system tools unable to traverse symlinked directories beyond top level

[G-bit94]

Describe the bug
The file system tools can't access child directories within a symlinked directory. While the tools can successfully list the contents of the symlinked directory itself, any attempt to access subdirectories results in an error claiming the parent directory doesn't exist.

To Reproduce
Steps to reproduce the behavior:

• Create a symbolic link to a directory (e.g., MCP_Servers in MCP_Root)
• Use file system tools to access the symlinked directory (succeeds)
• Attempt to access any subdirectory within the symlinked directory (fails)
• Error message states that the parent directory doesn't exist

Expected behavior
The file system tools should be able to traverse the entire directory structure through the symlink, not just the top level.

Logs
`> list_directory("F:/MCP_Root/MCP_Servers")
[DIR] .git
[FILE] .gitattributes
[DIR] .github
[FILE] .gitignore
[FILE] .npmrc
[FILE] CODE_OF_CONDUCT.md
[FILE] CONTRIBUTING.md
[FILE] LICENSE
[DIR] node_modules
[FILE] package-lock.json
[FILE] package.json
[FILE] README.md
[DIR] scripts
[FILE] SECURITY.md
[DIR] src
[FILE] tsconfig.json

list_directory("F:/MCP_Root/MCP_Servers/src")
Error: Parent directory does not exist: F:\MCP_Root\MCP_Servers

read_file("F:/MCP_Root/MCP_Servers/src/filesystem/README.md")
Error: Parent directory does not exist: F:\MCP_Root\MCP_Servers\src\filesystem`

Additional context
This issue prevents programmatic access to configuration details and documentation within the server implementation directories. The symlink appears to be valid as accessing the top-level directory works, but the link cannot be followed deeper into the structure.