Reload the godot-devtool editor plugin through the WebSocket bridge
AI agents invoke plugin_reload to trigger actions in Godot Devtool. 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.
Reloading an editor plugin is an external operation that triggers side effects in the Godot editor environment. It's not a simple read or write, but an action that restarts/reinitializes a plugin, which can affect the editor state. It uses the WebSocket bridge to trigger this operation remotely. This falls under Execute as it runs an external operation whose effects depend on the plugin state.
From the tool's definition 'Reload the godot-devtool editor plugin through the WebSocket bridge' — triggers an external operation (plugin reload) via WebSocket bridge
Documented attack patterns abuse exactly the kind of access plugin_reload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for plugin_reload:
{
"version": "1",
"default": "deny",
"tools": {
"plugin_reload": {
"limits": [
{
"counter": "plugin_reload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}plugin_reload 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.
Free to start. No card required.
Reload the godot-devtool editor plugin through the WebSocket bridge. It is categorised as a Execute tool in the Godot Devtool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for plugin_reload: 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 Devtool. Nothing to install.
plugin_reload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the plugin_reload 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 plugin_reload. 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.
plugin_reload is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.