gd_signature_help
Show the call signature(s) and active parameter at a position (the parameter hints an IDE pops up inside a call).
This record as markdown: /tools/godot-breakpoint-mcp/gd-signature-help.md
What gd_signature_help does on Godot Breakpoint
AI agents call gd_signature_help 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.
Why gd_signature_help is rated Low
This tool retrieves signature information for display purposes only, similar to IDE hover tooltips or parameter hints. It has no side effects, does not modify state, and does not execute code. It is purely informational, matching the Read category definition of retrieving or querying data with no side effects.
From the tool's definition Tool description states it 'Show[s] the call signature(s) and active parameter at a position', which is a read-only operation that retrieves and displays IDE parameter hints without modifying any data or triggering execution.
Attacks that exploit this kind of access
The rule that runs gd_signature_help 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 gd_signature_help, this is the rule to start with:
gd_signature_help 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 Breakpoint, apply this rule, and every gd_signature_help call is checked against it from then on.
Questions about gd_signature_help
Show the call signature(s) and active parameter at a position (the parameter hints an IDE pops up inside a call). It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for gd_signature_help: 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.
gd_signature_help 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 gd_signature_help 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 gd_signature_help. 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.
gd_signature_help 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.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue