Add a signal declaration to a GDScript file. Inserted after existing signals.
AI agents use add_signal to create or update resources in Godot Mcp Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Mcp Pilot environment.
This tool creates new signal declarations in GDScript files, which is a reversible modification (Write category). Severity is medium because: (1) it modifies project source code which could affect game behavior if misused, (2) the blast radius is localized to signal behavior rather than system-level, (3) changes are reversible and do not permanently delete data.
From the tool's definition Tool description states 'Add a signal declaration to a GDScript file. Inserted after existing signals.' The verb 'Add' and the action of inserting code into a file indicate creation/modification of data.
Attacks that exploit this kind of access
Add a signal declaration to a GDScript file. Inserted after existing signals. It is categorised as a Write tool in the Godot Mcp Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Mcp Pilot MCP server in PolicyLayer and add a rule for add_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 Mcp Pilot. Nothing to install.
add_signal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_signal is provided by the Godot Mcp Pilot MCP server (pushks18/godot-mcp-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →