ToolTrust
A2/100
juehang

vscode-mcp-server

mcp0.4.0

@juehang

MCP server to expose VS Code editing features to an LLM for AI coding

By juehang | 20 findings | Scanned 6/22/2026 | tooltrust-scanner/v0.3.19 | 374

2 Low18 Info

Risk Summary

Safe With Normal Controls

Excessive Permissions is the main signal, but overall risk remains within an acceptable range.

Potential impact: The agent may gain overly broad access to files, network, databases, or execution capabilities.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (20)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×2

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    execute_shell_commandcreate_diff

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-002

    ⚠️Excessive Permissions ×9

    declared capabilities: code/command execution, filesystem access

    execute_shell_commandcreate_diff

    declared capabilities: filesystem access

    open_fileopen_projectcheck_extension_statusget_extension_portlist_available_projectsget_active_tabsget_context_tabs

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×9

    No metadata.dependencies or repo_url were exposed by this MCP server, and no local project manifest could be inferred from the launch command.

    execute_shell_commandcreate_diffopen_fileopen_projectcheck_extension_statusget_extension_portlist_available_projectsget_active_tabsget_context_tabs

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y vscode-mcp-server"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)