webots_reset_controller_state · Webots MCP Server MCP

WHAT IT DOES

What webots_reset_controller_state does on Webots MCP Server

AI agents invoke webots_reset_controller_state to trigger actions in Webots MCP Server. 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 IT NEEDS A POLICY

Why webots_reset_controller_state needs a policy

Resetting a robot controller's internal state triggers an operation on the running simulation — it alters the controller's runtime state without reloading the world. This is an active intervention that changes simulation behavior, making it Execute. It is not purely destructive (no irreversible deletion) but misuse could disrupt ongoing simulation runs or cause unexpected robot behavior.

From the tool's definition 'Reset the robot controller's internal state without reloading the world'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webots_reset_controller_state Rate-limited

webots_reset_controller_state 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "webots_reset_controller_state": {
      "limits": [
        {
          "counter": "webots_reset_controller_state_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Webots MCP Server, so you can run agents against it safely.

FAQ

Questions about webots_reset_controller_state

What does the webots_reset_controller_state tool do? +

Reset the robot controller's internal state without reloading the world. It is categorised as a Execute tool in the Webots MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on webots_reset_controller_state? +

Register the Webots MCP Server MCP server in PolicyLayer and add a rule for webots_reset_controller_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 Webots MCP Server. Nothing to install.

What risk level is webots_reset_controller_state? +

webots_reset_controller_state is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit webots_reset_controller_state? +

Yes. Add a rate_limit block to the webots_reset_controller_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.

How do I block webots_reset_controller_state completely? +

Set action: deny in the PolicyLayer policy for webots_reset_controller_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.

What MCP server provides webots_reset_controller_state? +

webots_reset_controller_state 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.