Retrieves file contents with size limits and partial reading support. WHEN TO USE: Reading code, config files, analyzing implementations. Files >100k chars will fail. Encoding: Text encodings (utf-8, latin1, etc.) for text files,
AI agents call read_file_code 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 only retrieves and reads file contents without any side effects. It cannot write, delete, execute, or modify data. Even though it's part of a server with destructive and execute capabilities, this specific tool is a pure read operation with minimal blast radius if misused—worst case being unauthorized information disclosure of existing files.
From the tool's definition Tool name is 'read_file_code' and description states 'Retrieves file contents' with no capability to modify, delete, or execute. The use case explicitly lists 'Reading code, config files, analyzing implementations' as read-only operations.
Documented attack patterns abuse exactly the kind of access read_file_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vscode, and nothing reaches the server without passing your rules. This is the rule we recommend for read_file_code:
{
"version": "1",
"default": "deny",
"tools": {
"read_file_code": {}
}
}read_file_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves file contents with size limits and partial reading support. WHEN TO USE: Reading code, config files, analyzing implementations. Files >100k chars will fail. Encoding: Text encodings (utf-8, latin1, etc.) for text files,. 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 read_file_code: 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.
read_file_code 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 read_file_code 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 read_file_code. 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.
read_file_code is provided by the Vscode MCP server (juehang/vscode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vscode, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Vscode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.