emu_run_until
Step until TEXT appears in debug output emitted after the last emu_log call.
This record as markdown: /tools/3do-dev/emu-run-until.md
What emu_run_until does on 3do Dev
AI agents invoke emu_run_until to trigger actions in 3do Dev. 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 emu_run_until is rated High
Tool executes conditional stepping in emulator debugger, affecting program flow and state based on dynamic text matching.
From the tool's definition Step until TEXT appears in debug output; emulator control with conditional breakpoint logic
Attacks that exploit this kind of access
The rule that runs emu_run_until safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3do Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For emu_run_until, this is the rule to start with:
emu_run_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.
The button opens the PolicyLayer dashboard: create your workspace, connect 3do Dev, apply this rule, and every emu_run_until call is checked against it from then on.
Questions about emu_run_until
Step until TEXT appears in debug output emitted after the last emu_log call. It is categorised as a Execute tool in the 3do Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 3do Dev MCP server in PolicyLayer and add a rule for emu_run_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 3do Dev. Nothing to install.
emu_run_until 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 emu_run_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.
Set action: deny in the PolicyLayer policy for emu_run_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.
emu_run_until is provided by the 3do Dev MCP server (geekychris/3do-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3do Dev, and thousands of servers like it.
Across the catalogue