editor_disable_plugin · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_disable_plugin does on Godot

AI agents use editor_disable_plugin to create or update resources in Godot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.

PARAMETERS

Parameter	Type	Required	Description
`plugin`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_disable_plugin needs a policy

Disabling a plugin modifies the editor configuration/state by deactivating a plugin, which is a reversible write operation (the plugin can be re-enabled). It doesn't delete anything permanently, but it does change the editor's functional state.

From the tool's definition Disable a named editor plugin

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_disable_plugin Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_disable_plugin": {
      "limits": [
        {
          "counter": "editor_disable_plugin_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about editor_disable_plugin

What does the editor_disable_plugin tool do? +

Disable a named editor plugin. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does editor_disable_plugin accept? +

editor_disable_plugin accepts 1 parameter: plugin. Required: plugin. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_disable_plugin? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_disable_plugin: 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 Godot. Nothing to install.

What risk level is editor_disable_plugin? +

editor_disable_plugin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit editor_disable_plugin? +

Yes. Add a rate_limit block to the editor_disable_plugin 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 editor_disable_plugin completely? +

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

editor_disable_plugin is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.