find_ui_elements
🔴 Game must be running. Find UI elements in the running game by type, text, or name
This record as markdown: /tools/keeveeg-godot-mcp/find-ui-elements.md
What find_ui_elements does on Godot
AI agents call find_ui_elements 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 |
|---|---|---|---|
filter | object | — | Filter criteria for UI element search |
Parameters from the server's own tool schema.
Why find_ui_elements is rated Low
The tool retrieves information about UI elements from a running Godot game without modifying, deleting, or executing operations. This is a read-only information retrieval function, which poses minimal security risk when used as intended.
From the tool's definition Tool description states 'Find UI elements in the running game by type, text, or name' — a query/search operation with no side effects mentioned.
Attacks that exploit this kind of access
The rule that runs find_ui_elements 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 find_ui_elements, this is the rule to start with:
find_ui_elements 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 find_ui_elements call is checked against it from then on.
Questions about find_ui_elements
🔴 Game must be running. Find UI elements in the running game by type, text, or name. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
find_ui_elements accepts 1 parameter: filter. 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 find_ui_elements: 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.
find_ui_elements 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 find_ui_elements 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 find_ui_elements. 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.
find_ui_elements is provided by the Godot MCP server (@keeveeg/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