emu_state
Save or load a full machine snapshot (action save|load).
This record as markdown: /tools/3do-dev/emu-state.md
What emu_state does on 3do Dev
AI agents use emu_state to create or update resources in 3do Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 3do Dev environment.
Why emu_state is rated Medium
Modifies emulator state reversibly; high blast radius if overwritten without consent.
From the tool's definition Save or load a full machine snapshot (action save|load).
Attacks that exploit this kind of access
The rule that runs emu_state 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_state, this is the rule to start with:
emu_state stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_state call is checked against it from then on.
Questions about emu_state
Save or load a full machine snapshot (action save|load). It is categorised as a Write tool in the 3do Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 3do Dev MCP server in PolicyLayer and add a rule for emu_state: 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_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the emu_state 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_state. 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_state 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