AI agents call editor_list_node_signals to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
node | string | Yes |
Parameters from the server's own tool schema.
This tool queries and retrieves information about signals and their connections on a Godot node. The verb 'list' and the context of inspecting node properties indicate this is a read-only operation that does not modify state, execute code, or trigger side effects. The low severity reflects minimal risk even if misused by an agent, as it only exposes metadata about the scene graph.
From the tool's definition Tool name contains 'list' and description states 'List signals and their connections on a node' — purely informational retrieval with no modification or execution.
Attacks that exploit this kind of access
List signals and their connections on a node. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
editor_list_node_signals accepts 1 parameter: node. Required: node. 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 editor_list_node_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.
editor_list_node_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 editor_list_node_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 editor_list_node_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.
editor_list_node_signals 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.
editor_list_node_signals is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →