assert_screen_text

Assert that specific text appears on screen (OCR or UI element check)

SERVERGodot SOURCE@keeveeg/godot-mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/assert-screen-text.md

WHAT IT DOES

What assert_screen_text does on Godot

AI agents use assert_screen_text to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.

Parameter	Type	Required	Description
`text`	string	Yes	Text that should appear on screen
`should_exist`	boolean	—	Whether text should be present (true) or absent (false) (default: true)

Parameters from the server's own tool schema.

RISK

Why assert_screen_text is rated Medium

An AI agent can call assert_screen_text faster than any human can review: one bad instruction and it creates or modifies resources in Godot by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs assert_screen_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 assert_screen_text, this is the rule to start with:

assert_screen_text Rate-limited

assert_screen_text stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "assert_screen_text": {
      "limits": [
        {
          "counter": "assert_screen_text_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every assert_screen_text call is checked against it from then on.

FAQ

Questions about assert_screen_text

What does the assert_screen_text tool do? +

Assert that specific text appears on screen (OCR or UI element check). It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does assert_screen_text accept? +

assert_screen_text accepts 2 parameters: text, should_exist. Required: text. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on assert_screen_text? +

Register the Godot 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. Nothing to install.

What risk level is assert_screen_text? +

assert_screen_text is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit assert_screen_text? +

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.

How do I block assert_screen_text completely? +

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.

What MCP server provides assert_screen_text? +

assert_screen_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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 321 Godot tools →

Across the catalogue

edit_screen on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →