signal_list_node_signals
A read tool on the Godot MCP server.
This record as markdown: /tools/chanceflow-godot-mcp/signal-list-node-signals.md
What signal_list_node_signals does on Godot
AI agents call signal_list_node_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.
Why signal_list_node_signals is rated Low
The tool appears to retrieve or enumerate signals from a Godot scene node, which is a non-destructive query operation. The naming convention (list) and context within a game engine API strongly suggests data retrieval with no side effects. Although the description is empty, the tool name and sibling context provide sufficient evidence for high confidence classification as Read.
From the tool's definition Tool name 'signal_list_node_signals' indicates a listing/querying operation on Godot node signals; no parameters described that would suggest modification or execution.
Attacks that exploit this kind of access
The rule that runs signal_list_node_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 signal_list_node_signals, this is the rule to start with:
signal_list_node_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 signal_list_node_signals call is checked against it from then on.
Questions about signal_list_node_signals
signal_list_node_signals is a read tool on the Godot MCP server. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for signal_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.
signal_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 signal_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 signal_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.
signal_list_node_signals is provided by the Godot MCP server (chanceflow/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