This record as markdown: /tools/yanhuifair-godot-mcp/list-all-signals.md
What list_all_signals does on Godot
AI agents call list_all_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 |
|---|---|---|---|
scene_path | object | — | Filter to scene |
signal_name | object | — | Filter by signal name |
Parameters from the server's own tool schema.
Why list_all_signals is rated Low
This tool performs only data retrieval—it queries and returns information about existing signal connections in the Godot project. There are no side effects, no state changes, no code execution, and no destructive actions. It is a straightforward informational read operation, making it the lowest severity risk category.
From the tool's definition Tool name is 'list_all_signals' and description states 'List all signal connections across scenes.' The verb 'list' and the retrieval-focused description indicate a read-only query operation that retrieves signal connection metadata without modifying,…
Attacks that exploit this kind of access
The rule that runs list_all_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 list_all_signals, this is the rule to start with:
list_all_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 list_all_signals call is checked against it from then on.
Questions about list_all_signals
List all signal connections across scenes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
list_all_signals accepts 2 parameters: scene_path, signal_name. 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 list_all_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.
list_all_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 list_all_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 list_all_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.
list_all_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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue