High Risk →

until

Run until a specified location or next source line (MI -exec-until).

How to control until ↓

AI agents invoke until to trigger actions in Pwno. 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.

High Risk

This tool executes debugger control flow commands via GDB's MI interface. While it does not directly execute arbitrary code or shell commands, it manipulates the execution state of a debugged binary in a stateful debugging system.

From the tool's definition Tool description states 'Run until a specified location or next source line (MI -exec-until)', indicating execution of debugger commands that control program flow during a debugging session.

Documented attack patterns abuse exactly the kind of access until gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for until:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "until": {
      "limits": [
        {
          "counter": "until_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Pwno — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the until tool do? +

Run until a specified location or next source line (MI -exec-until). It is categorised as a Execute tool in the Pwno MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on until? +

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

What risk level is until? +

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

Can I rate-limit until? +

Yes. Add a rate_limit block to the until 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 until completely? +

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

until is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pwno tool call.

Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.