find_signal_connections
Find all signal connections in the scene
This record as markdown: /tools/keeveeg-godot-mcp/find-signal-connections.md
What find_signal_connections does on Godot
AI agents call find_signal_connections 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 find_signal_connections is rated Low
This tool performs a read-only operation that queries and returns data about signal connections in a Godot scene. It has no side effects, does not modify state, and does not execute code or delete data. It falls squarely into the Read category as a data retrieval/search function.
From the tool's definition Tool name 'find_signal_connections' and description 'Find all signal connections in the scene' indicate a query/search operation that retrieves information about existing signal connections without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs find_signal_connections 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 find_signal_connections, this is the rule to start with:
find_signal_connections 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 find_signal_connections call is checked against it from then on.
Questions about find_signal_connections
Find all signal connections in the scene. 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 find_signal_connections: 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.
find_signal_connections 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 find_signal_connections 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 find_signal_connections. 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.
find_signal_connections 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