signal_list

List the signals a node declares (name and argument names), including user signals. Read-only.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-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/godot-breakpoint-mcp/signal-list.md

WHAT IT DOES

What signal_list does on Godot Breakpoint

AI agents call signal_list to retrieve information from Godot Breakpoint 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 is rated Low

The tool retrieves and lists signal declarations from a Godot node without modifying, deleting, or executing any operations. This is a straightforward data query operation with no blast radius if misused by an AI agent.

From the tool's definition Tool description explicitly states 'Read-only' and lists signals (retrieves data with no side effects).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signal_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For signal_list, this is the rule to start with:

signal_list Allowed

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

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

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

FAQ

Questions about signal_list

What does the signal_list tool do? +

List the signals a node declares (name and argument names), including user signals. Read-only. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on signal_list? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for signal_list: 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 Breakpoint. Nothing to install.

What risk level is signal_list? +

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

Can I rate-limit signal_list? +

Yes. Add a rate_limit block to the signal_list 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 completely? +

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

signal_list is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-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 Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint 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 →