Dump the full DOM structure to a file (JSON, HTML, or tree format). The AI can then read sections of this file incrementally to explore large DOMs without overwhelming context.
AI agents use vscode_dump_dom_to_file to create or update resources in VSCode Automation MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VSCode Automation MCP environment.
This tool writes data to a file on disk. While it's fundamentally reading the DOM structure, the primary action is writing/creating a file, making it a Write operation. Severity is medium because it writes files to the filesystem, which could overwrite existing files depending on path arguments, but is generally reversible.
From the tool's definition Dump the full DOM structure to a file (JSON, HTML, or tree format)
Documented attack patterns abuse exactly the kind of access vscode_dump_dom_to_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VSCode Automation MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for vscode_dump_dom_to_file:
{
"version": "1",
"default": "deny",
"tools": {
"vscode_dump_dom_to_file": {
"limits": [
{
"counter": "vscode_dump_dom_to_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}vscode_dump_dom_to_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Dump the full DOM structure to a file (JSON, HTML, or tree format). The AI can then read sections of this file incrementally to explore large DOMs without overwhelming context. It is categorised as a Write tool in the VSCode Automation MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VSCode Automation MCP server in PolicyLayer and add a rule for vscode_dump_dom_to_file: 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 Automation MCP. Nothing to install.
vscode_dump_dom_to_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vscode_dump_dom_to_file 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 vscode_dump_dom_to_file. 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.
vscode_dump_dom_to_file is provided by the VSCode Automation MCP server (sukarth/vscode-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VSCode Automation MCP, 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.
61 VSCode Automation MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.