get_signals

Get all signals and their connections for a node

SERVERGodot SOURCE@keeveeg/godot-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/get-signals.md

WHAT IT DOES

What get_signals does on Godot

AI agents call get_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
`node_path`	string	Yes	Node path to inspect

Parameters from the server's own tool schema.

RISK

Why get_signals is rated Low

This tool retrieves information about signals and connections in a Godot scene without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects on the project state.

From the tool's definition Tool name is 'get_signals' and description states 'Get all signals and their connections for a node' — indicates retrieval/query of existing data with no modifications

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_signals Allowed

get_signals 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": {
    "get_signals": {}
  }
}

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 get_signals call is checked against it from then on.

FAQ

Questions about get_signals

What does the get_signals tool do? +

Get all signals and their connections for a node. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

What parameters does get_signals accept? +

get_signals accepts 1 parameter: node_path. Required: node_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_signals? +

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

What risk level is get_signals? +

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

Can I rate-limit get_signals? +

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

How do I block get_signals completely? +

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

What MCP server provides get_signals? +

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

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 321 Godot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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