editor_enable_plugin · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_enable_plugin does on Godot

AI agents invoke editor_enable_plugin to trigger actions in Godot. 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.

PARAMETERS

Parameter	Type	Required	Description
`plugin`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_enable_plugin needs a policy

Enabling a plugin triggers external code execution within the Godot editor environment. It is not merely writing data—it activates a plugin module whose effects depend on which plugin is named. This is an external operation with side effects beyond simple data modification, justifying the Execute category.

From the tool's definition Enable a named editor plugin

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_enable_plugin Rate-limited

editor_enable_plugin 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": {
    "editor_enable_plugin": {
      "limits": [
        {
          "counter": "editor_enable_plugin_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 Godot, so you can run agents against it safely.

FAQ

Questions about editor_enable_plugin

What does the editor_enable_plugin tool do? +

Enable a named editor plugin. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does editor_enable_plugin accept? +

editor_enable_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_enable_plugin? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_enable_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_enable_plugin? +

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

Can I rate-limit editor_enable_plugin? +

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

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

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