connect_signal · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_signal does on Godot MCP Server

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

WHY IT NEEDS A POLICY

Why connect_signal needs a policy

Signal connections in Godot are reversible modifications that alter how nodes communicate but do not execute arbitrary code, delete data, or cause external effects. The action creates a new connection between existing nodes—a Write operation.

From the tool's definition Tool description states 'Connect a signal from one node to a method on another node.' This modifies the scene graph by establishing a new signal connection, which is a reversible change to game logic wiring.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_signal Rate-limited

connect_signal 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": {
    "connect_signal": {
      "limits": [
        {
          "counter": "connect_signal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 connect_signal

What does the connect_signal tool do? +

Connect a signal from one node to a method on another node. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_signal? +

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

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

Can I rate-limit connect_signal? +

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

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

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