This record as markdown: /tools/yanhuifair-godot-mcp/list-ui-nodes.md
What list_ui_nodes does on Godot
AI agents call list_ui_nodes to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
node_type | object | — | Filter by specific Control type (e.g. "Button", "Label"). Default: all Control-derived nodes. |
max_results | object | — | Max results |
Parameters from the server's own tool schema.
Why list_ui_nodes is rated Low
This tool retrieves and enumerates UI nodes in the Godot scene hierarchy. It performs no modifications, deletions, or code execution. The operation is read-only with no side effects. Severity is low because listing UI nodes exposes only structural information about the game project with no capacity for harm.
From the tool's definition Tool name 'list_ui_nodes' and description 'List Control-derived UI nodes' indicate a query/retrieval operation that lists existing UI nodes without modifying state.
Attacks that exploit this kind of access
The rule that runs list_ui_nodes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_ui_nodes, this is the rule to start with:
list_ui_nodes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every list_ui_nodes call is checked against it from then on.
Questions about list_ui_nodes
List Control-derived UI nodes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
list_ui_nodes accepts 2 parameters: node_type, max_results. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for list_ui_nodes: 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.
list_ui_nodes 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_ui_nodes 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_ui_nodes. 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_ui_nodes 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue