Get the direct children (or descendants) of an element. Use this for incremental DOM exploration - start with a parent, then drill down into specific children.
AI agents call vscode_get_element_children to retrieve information from VSCode Automation MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries the DOM tree of VSCode's UI without side effects. It enables exploration and inspection of UI structure but does not execute commands, modify state, or trigger external operations. The blast radius is minimal—worst case, an agent maps the UI structure unnecessarily, which has no material impact on the system.
From the tool's definition Tool retrieves DOM structure information: 'Get the direct children (or descendants) of an element.' No modification, deletion, or command execution occurs.
Documented attack patterns abuse exactly the kind of access vscode_get_element_children 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_get_element_children:
{
"version": "1",
"default": "deny",
"tools": {
"vscode_get_element_children": {}
}
}vscode_get_element_children 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.
Get the direct children (or descendants) of an element. Use this for incremental DOM exploration - start with a parent, then drill down into specific children. It is categorised as a Read tool in the VSCode Automation MCP MCP Server, which means it retrieves data without modifying state.
Register the VSCode Automation MCP server in PolicyLayer and add a rule for vscode_get_element_children: 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_get_element_children 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 vscode_get_element_children 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_get_element_children. 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_get_element_children 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.