signal_list_connections

A read tool on the Godot MCP server.

SERVERGodot SOURCEchanceflow/godot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/chanceflow-godot-mcp/signal-list-connections.md

WHAT IT DOES

What signal_list_connections does on Godot

AI agents call signal_list_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.

RISK

Why signal_list_connections is rated Low

This tool retrieves and enumerates existing signal connections within the Godot engine, which is a query operation with no capacity to modify state. While the description is empty, the naming convention and context (alongside other introspection tools) strongly indicate a read-only listing function. Misuse would expose internal engine structure but carry minimal blast radius.

From the tool's definition Tool name 'signal_list_connections' indicates listing/retrieving signal connections; no verbs like 'create', 'delete', 'modify', or 'execute' suggest side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signal_list_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 signal_list_connections, this is the rule to start with:

signal_list_connections Allowed

signal_list_connections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "signal_list_connections": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every signal_list_connections call is checked against it from then on.

FAQ

Questions about signal_list_connections

What does the signal_list_connections tool do? +

signal_list_connections 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.

How do I enforce a policy on signal_list_connections? +

Register the Godot MCP server in PolicyLayer and add a rule for signal_list_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.

What risk level is signal_list_connections? +

signal_list_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit signal_list_connections? +

Yes. Add a rate_limit block to the signal_list_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.

How do I block signal_list_connections completely? +

Set action: deny in the PolicyLayer policy for signal_list_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.

What MCP server provides signal_list_connections? +

signal_list_connections 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 84 Godot tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →