List Godot game/editor run instances managed by this MCP server
AI agents call list_run_instances 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 retrieves information about currently running Godot instances without modifying, executing, or deleting anything. It is a simple informational query operation. The low severity reflects minimal risk even if an AI agent calls it; it only returns state information about the server's managed processes.
From the tool's definition Tool name 'list_run_instances' and description 'List Godot game/editor run instances' indicate a query/retrieval operation with no side effects. The verb 'list' is explicitly enumerated in the Read category definition.
Documented attack patterns abuse exactly the kind of access list_run_instances 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 list_run_instances:
{
"version": "1",
"default": "deny",
"tools": {
"list_run_instances": {}
}
}list_run_instances 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.
List Godot game/editor run instances managed by this MCP server. 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 list_run_instances: 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.
list_run_instances 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 list_run_instances 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 list_run_instances. 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.
list_run_instances 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.