detect_vscode_workspaces
Automatically detect open VS Code instances and their workspaces
This record as markdown: /tools/agentics-ai-code-mcp/detect-vscode-workspaces.md
What detect_vscode_workspaces does on Code MCP Server
AI agents call detect_vscode_workspaces to retrieve information from Code MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why detect_vscode_workspaces is rated Low
This tool retrieves information about running VS Code instances and their workspace configurations. It performs discovery and enumeration without any side effects—no data is created, modified, deleted, or executed. This is a pure read operation that returns environmental state information.
From the tool's definition Tool name 'detect_vscode_workspaces' and description 'Automatically detect open VS Code instances and their workspaces' indicate querying/discovery of existing workspace metadata with no modification, creation, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs detect_vscode_workspaces safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_vscode_workspaces, this is the rule to start with:
detect_vscode_workspaces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every detect_vscode_workspaces call is checked against it from then on.
Questions about detect_vscode_workspaces
Automatically detect open VS Code instances and their workspaces. It is categorised as a Read tool in the Code MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for detect_vscode_workspaces: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Code MCP Server. Nothing to install.
detect_vscode_workspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the detect_vscode_workspaces rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for detect_vscode_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.
detect_vscode_workspaces is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
This server
Across the catalogue