AI agents call get_workspace_info to retrieve information from Vscode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves workspace metadata without side effects. It queries existing state (git status summary, environment info) rather than executing code, modifying files, or triggering external operations. The sibling tools include destructive capabilities (create_directory, cursor_run_command), but this tool itself is strictly informational.
From the tool's definition Tool description states it 'Get[s] information about the current workspace' including root directory, platform, Node version, and git status summary. These are all read-only queries with no modification or execution of commands.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get information about the current workspace: root directory, platform, Node version, git status summary. It is categorised as a Read tool in the Vscode MCP Server, which means it retrieves data without modifying state.
Register the Vscode MCP server in PolicyLayer and add a rule for get_workspace_info: 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 Vscode. Nothing to install.
get_workspace_info 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 get_workspace_info 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 get_workspace_info. 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.
get_workspace_info is provided by the Vscode MCP server (kloutdevs/vscode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_workspace_info is one line of Vscode's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →