step_to_next_hit · Pernosco MCP: Risk & Policy

WHAT IT DOES

What step_to_next_hit does on Pernosco

AI agents invoke step_to_next_hit to trigger actions in Pernosco. 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 IT NEEDS A POLICY

Why step_to_next_hit needs a policy

This tool triggers navigation/execution control within a debugging session, advancing the program state to the next hit of a source line. It actively drives execution flow rather than passively reading data, making it an Execute-category action.

From the tool's definition Navigate forward to the next execution... stepping through loop iterations or repeated calls

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

step_to_next_hit Rate-limited

step_to_next_hit 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "step_to_next_hit": {
      "limits": [
        {
          "counter": "step_to_next_hit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pernosco, so you can run agents against it safely.

FAQ

Questions about step_to_next_hit

What does the step_to_next_hit tool do? +

Navigate forward to the next execution of the current source line (or a specified line). Useful for stepping through loop iterations or repeated calls. It is categorised as a Execute tool in the Pernosco MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on step_to_next_hit? +

Register the Pernosco MCP server in PolicyLayer and add a rule for step_to_next_hit: 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 Pernosco. Nothing to install.

What risk level is step_to_next_hit? +

step_to_next_hit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit step_to_next_hit? +

Yes. Add a rate_limit block to the step_to_next_hit 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.

How do I block step_to_next_hit completely? +

Set action: deny in the PolicyLayer policy for step_to_next_hit. 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.

What MCP server provides step_to_next_hit? +

step_to_next_hit is provided by the Pernosco MCP server (jnjaeschke/pernosco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.