Erases all content and settings from the booted simulator (destructive operation).
AI agents call erase_simulator to permanently remove resources in MCP Connect — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes or overwrites data on a simulator by erasing all content and settings. It cannot be undone and has a significant blast radius if triggered unintentionally by an AI agent. While the impact is scoped to a simulator environment rather than production systems, the total data loss on that simulator is permanent, justifying the Destructive category and high severity.
From the tool's definition Tool name is 'erase_simulator' and description explicitly states 'Erases all content and settings from the booted simulator (destructive operation).'
Attacks that exploit this kind of access
Erases all content and settings from the booted simulator (destructive operation). It is categorised as a Destructive tool in the MCP Connect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Connect MCP server in PolicyLayer and add a rule for erase_simulator: 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 MCP Connect. Nothing to install.
erase_simulator is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the erase_simulator 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 erase_simulator. 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.
erase_simulator is provided by the MCP Connect MCP server (plaintest/mcp-connect). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →