Low Risk

list_workspaces

List all available VSCode workspaces that can be connected to use vscode mcp tools **Return Format:** Array of workspace objects with paths, names, status, and optional details. Includes summary statistics about discovered workspaces. **Important Notes:** - **Active status** means successfully ...

Part of the Vscode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call list_workspaces to retrieve information from Vscode without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_workspaces only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

vscode.yaml
tools:
  list_workspaces:
    rules:
      - action: allow

See the full Vscode policy for all 8 tools.

Tool Name list_workspaces
Category Read
MCP Server Vscode MCP Server
Risk Level Low
What does the list_workspaces tool do? +

List all available VSCode workspaces that can be connected to use vscode mcp tools **Return Format:** Array of workspace objects with paths, names, status, and optional details. Includes summary statistics about discovered workspaces. **Important Notes:** - **Active status** means successfully connected and verified - **Available status** means socket exists but not tested. It is categorised as a Read tool in the Vscode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_workspaces? +

Add a rule in your Intercept YAML policy under the tools section for list_workspaces. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Vscode MCP server.

What risk level is list_workspaces? +

list_workspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_workspaces? +

Yes. Add a rate_limit block to the list_workspaces rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block list_workspaces completely? +

Set action: deny in the Intercept policy for list_workspaces. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides list_workspaces? +

list_workspaces is provided by the Vscode MCP server (@vscode-mcp/vscode-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Vscode

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.