Read godot-devtool plugin installation status, WebSocket bridge configuration, connected clients, and occupied-port diagnostics
AI agents call plugin_status to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves diagnostic and configuration status information about the plugin, WebSocket bridge, and connected clients. No data is modified, executed, or deleted. It is a passive read operation suitable for inspection and troubleshooting, placing it squarely in the Read category with low severity.
From the tool's definition Tool name is 'plugin_status' and description states it 'Read[s] godot-devtool plugin installation status, WebSocket bridge configuration, connected clients, and occupied-port diagnostics' — pure inspection/query with no modification, execution, or side…
Documented attack patterns abuse exactly the kind of access plugin_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"plugin_status": {}
}
}plugin_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read godot-devtool plugin installation status, WebSocket bridge configuration, connected clients, and occupied-port diagnostics. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for plugin_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plugin_status 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_status. 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_status 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.