dismiss_dialogs · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What dismiss_dialogs does on Godot MCP Server

AI agents invoke dismiss_dialogs 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.

WHY IT NEEDS A POLICY

Why dismiss_dialogs needs a policy

This tool triggers an action in the Godot editor UI — dismissing modal dialogs. It executes an external operation (interacting with the editor's UI state) whose effects depend on what dialogs are open. While it doesn't directly delete data, dismissing a dialog could cancel important pending actions, confirm/abort operations, or discard unsaved changes depending on context.

From the tool's definition Dismiss any open modal dialogs in the Godot editor

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dismiss_dialogs Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dismiss_dialogs": {
      "limits": [
        {
          "counter": "dismiss_dialogs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about dismiss_dialogs

What does the dismiss_dialogs tool do? +

Dismiss any open modal dialogs in the Godot editor. 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.

How do I enforce a policy on dismiss_dialogs? +

Register the Godot MCP Server MCP server in PolicyLayer and add a rule for dismiss_dialogs: 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.

What risk level is dismiss_dialogs? +

dismiss_dialogs is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dismiss_dialogs? +

Yes. Add a rate_limit block to the dismiss_dialogs 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 dismiss_dialogs completely? +

Set action: deny in the PolicyLayer policy for dismiss_dialogs. 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 dismiss_dialogs? +

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