Install the godot-devtool WebSocket editor/runtime plugin into a Godot project
AI agents use plugin_install to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool writes plugin files into a Godot project directory, modifying the project's file structure. It is a Write operation as it creates/installs files. Severity is high because installing a WebSocket editor/runtime plugin could introduce persistent code execution capabilities into the project, and if misused could install malicious or unintended plugins into production projects.
From the tool's definition 'Install the godot-devtool WebSocket editor/runtime plugin into a Godot project'
Documented attack patterns abuse exactly the kind of access plugin_install 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_install:
{
"version": "1",
"default": "deny",
"tools": {
"plugin_install": {
"limits": [
{
"counter": "plugin_install_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}plugin_install 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.
Free to start. No card required.
Install the godot-devtool WebSocket editor/runtime plugin into a Godot project. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for plugin_install: 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_install is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plugin_install 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_install. 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_install 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.