watch_signals
🔴 Game must be running. Watch for signal emissions from a game node
This record as markdown: /tools/keeveeg-godot-mcp/watch-signals.md
What watch_signals does on Godot
AI agents call watch_signals to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path to watch |
signals | array | Yes | Signal names to watch for |
duration | number | — | How long to watch in seconds |
Parameters from the server's own tool schema.
Why watch_signals is rated Low
The tool watches/listens for signal emissions, which is a read/observe operation with no side effects. It does not modify game state, create data, or execute commands. Severity is low as it only monitors runtime events.
From the tool's definition 'Watch for signal emissions from a game node' — passively observes/monitors signals without modifying state
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs watch_signals 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 watch_signals, this is the rule to start with:
watch_signals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every watch_signals call is checked against it from then on.
Questions about watch_signals
🔴 Game must be running. Watch for signal emissions from a game node. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
watch_signals accepts 3 parameters: path, signals, duration. Required: path, signals. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for watch_signals: 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.
watch_signals is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the watch_signals 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 watch_signals. 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.
watch_signals 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue