Assert that a given text string appears on the screen within a timeout.
AI agents invoke assert_screen_text to trigger actions in Godot MCP Server. 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.
This tool triggers an assertion check — an active verification operation within the Godot editor/runtime that waits up to a timeout period. It executes a polling/waiting action against the running game or editor state rather than simply reading data passively. It could cause test failures or block execution flows if misused, placing it in Execute.
From the tool's definition Assert that a given text string appears on the screen within a timeout
Attacks that exploit this kind of access
Assert that a given text string appears on the screen within a timeout. It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for assert_screen_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 MCP Server. Nothing to install.
assert_screen_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 assert_screen_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 assert_screen_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.
assert_screen_text is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →