emu_crashes
Aborts / exceptions the 3DO OS reported, with registers and log context.
This record as markdown: /tools/3do-dev/emu-crashes.md
What emu_crashes does on 3do Dev
AI agents call emu_crashes to retrieve information from 3do Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why emu_crashes is rated Low
Retrieves crash/exception log data from the emulator; no side effects.
From the tool's definition Aborts / exceptions the 3DO OS reported, with registers and log context
Attacks that exploit this kind of access
The rule that runs emu_crashes 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_crashes, this is the rule to start with:
emu_crashes is read-only, so it stays allowed. 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_crashes call is checked against it from then on.
Questions about emu_crashes
Aborts / exceptions the 3DO OS reported, with registers and log context. It is categorised as a Read tool in the 3do Dev MCP Server, which means it retrieves data without modifying state.
Register the 3do Dev MCP server in PolicyLayer and add a rule for emu_crashes: 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_crashes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the emu_crashes 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_crashes. 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_crashes 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.
This server
Across the catalogue