step_over
Steps over to the next statement, treating function calls as a single step. Use this to move through code without entering function bodies.
This record as markdown: /tools/1600822305-js-reverse-mcp/step-over.md
What step_over does on Js Reverse
AI agents invoke step_over to trigger actions in Js Reverse. 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.
Why step_over is rated High
This tool controls browser debugger execution flow via Chrome DevTools Protocol, advancing the execution pointer in a running JavaScript debug session. It triggers an external operation (browser/debugger state change) and is part of a broader code execution control context. It doesn't just read data — it actively steps execution forward in the browser process.
From the tool's definition Steps over to the next statement, treating function calls as a single step. Use this to move through code without entering function bodies.
Attacks that exploit this kind of access
The rule that runs step_over safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For step_over, this is the rule to start with:
step_over 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every step_over call is checked against it from then on.
Questions about step_over
Steps over to the next statement, treating function calls as a single step. Use this to move through code without entering function bodies. It is categorised as a Execute tool in the Js Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Js Reverse MCP server in PolicyLayer and add a rule for step_over: 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 Js Reverse. Nothing to install.
step_over 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 step_over 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 step_over. 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.
step_over is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
Across the catalogue