add_script_signal · Godot MCP: Risk & Policy

WHAT IT DOES

What add_script_signal does on Godot

AI agents use add_script_signal 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.

PARAMETERS

Parameter	Type	Required	Description
`path`	string	Yes	Path to .gd script file
`params`	object	—	Signal parameters
`signal_name`	string	Yes	Signal name

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why add_script_signal needs a policy

This tool creates a new signal declaration in GDScript code, which modifies the script file structure. While signals are fundamental to Godot's event system, the operation is reversible (the signal declaration can be removed or edited). It does not execute code, delete data irreversibly, or move money.

From the tool's definition Tool name 'add_script_signal' and description 'Add a signal declaration to GDScript' indicate creating/modifying a script by adding a signal declaration. This is a reversible creation operation on a script file.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_script_signal Rate-limited

add_script_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": {
    "add_script_signal": {
      "limits": [
        {
          "counter": "add_script_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, so you can run agents against it safely.

FAQ

Questions about add_script_signal

What does the add_script_signal tool do? +

Add a signal declaration to GDScript. 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 add_script_signal accept? +

add_script_signal accepts 3 parameters: path, params, signal_name. Required: path, signal_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_script_signal? +

Register the Godot MCP server in PolicyLayer and add a rule for add_script_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. Nothing to install.

What risk level is add_script_signal? +

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

Can I rate-limit add_script_signal? +

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

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

add_script_signal is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.