click_button_by_text
🔴 Game must be running. Find and click a button by its text content
This record as markdown: /tools/keeveeg-godot-mcp/click-button-by-text.md
What click_button_by_text does on Godot
AI agents invoke click_button_by_text to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Button text to find and click |
timeout | number | — | Timeout in seconds |
Parameters from the server's own tool schema.
Why click_button_by_text is rated High
This tool performs a UI interaction (clicking a button) within a running game environment. It triggers external operations whose effects depend on which button is clicked, which could cause any number of in-game or engine-level actions. The '🔴 Game must be running' note confirms it operates on a live running process.
From the tool's definition Find and click a button by its text content
Attacks that exploit this kind of access
The rule that runs click_button_by_text 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 click_button_by_text, this is the rule to start with:
click_button_by_text stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 click_button_by_text call is checked against it from then on.
Questions about click_button_by_text
🔴 Game must be running. Find and click a button by its text content. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
click_button_by_text accepts 2 parameters: text, timeout. Required: text. 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 click_button_by_text: 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.
click_button_by_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the click_button_by_text 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 click_button_by_text. 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.
click_button_by_text 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.
Across the catalogue