Reset the simulation to initial state (keeps world loaded).
AI agents call webots_world_reset to permanently remove resources in Webots MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Resetting the simulation to its initial state is an irreversible destructive action — all current simulation progress, robot positions, sensor states, and runtime data are wiped and cannot be recovered. While the world file remains loaded, the current simulation state is permanently discarded. This maps to Destructive rather than Execute because the outcome is fixed (reset to initial state) regardless of arguments.
From the tool's definition Reset the simulation to initial state
Attacks that exploit this kind of access
Reset the simulation to initial state (keeps world loaded). It is categorised as a Destructive tool in the Webots MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Webots MCP Server MCP server in PolicyLayer and add a rule for webots_world_reset: 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 Webots MCP Server. Nothing to install.
webots_world_reset 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 webots_world_reset 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 webots_world_reset. 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.
webots_world_reset is provided by the Webots MCP Server MCP server (luisfelipesena/webots-youbot-mcp). 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 →