Step over the current line of code (execute current line without entering functions)
AI agents invoke debug_stepOver to trigger actions in MCP Server for VS Code. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes code as part of debugger control flow. While it does not directly run arbitrary code, it progresses execution of an already-loaded program, which is an Execute-class action with potential side effects depending on what the current line does (I/O, state modification, external calls).
From the tool's definition Tool name 'debug_stepOver' and description 'Step over the current line of code (execute current line without entering functions)' indicates execution of code during debugging.
Documented attack patterns abuse exactly the kind of access debug_stepOver gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for VS Code, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_stepOver:
{
"version": "1",
"default": "deny",
"tools": {
"debug_stepOver": {
"limits": [
{
"counter": "debug_stepover_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}debug_stepOver stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Step over the current line of code (execute current line without entering functions). It is categorised as a Execute tool in the MCP Server for VS Code MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Server for VS Code MCP server in PolicyLayer and add a rule for debug_stepOver: 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 MCP Server for VS Code. Nothing to install.
debug_stepOver is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the debug_stepOver 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 debug_stepOver. 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.
debug_stepOver is provided by the MCP Server for VS Code MCP server (malvex/mcp-server-vscode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for VS Code, 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.
25 MCP Server for VS Code tools catalogued and risk-classified — across an index of 43,000+ MCP servers.