runtime_emit_signal

Emit a signal from a live node. DESTRUCTIVE — gated by confirmation.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/runtime-emit-signal.md

What runtime_emit_signal does on Godot Breakpoint

AI agents invoke runtime_emit_signal to trigger actions in Godot Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why runtime_emit_signal is rated High

Emitting a signal on a live Godot node triggers arbitrary runtime callbacks and side effects depending on what is connected to that signal. This is an Execute-category action (triggers external operations whose effects depend on arguments).

From the tool's definition 'Emit a signal from a live node. DESTRUCTIVE — gated by confirmation.'

Questions about runtime_emit_signal

What does the runtime_emit_signal tool do? +

Emit a signal from a live node. DESTRUCTIVE — gated by confirmation. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on runtime_emit_signal? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for runtime_emit_signal: 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 runtime_emit_signal? +

runtime_emit_signal is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit runtime_emit_signal? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Godot Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.