This record as markdown: /tools/yanhuifair-godot-mcp/editor-add-input-action.md
What editor_add_input_action does on Godot
AI agents use editor_add_input_action to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
deadzone | object | — |
Parameters from the server's own tool schema.
Why editor_add_input_action is rated Medium
This tool creates or modifies input action bindings in a Godot project, which is a reversible Write operation. While it modifies project configuration, the changes can be undone via the editor. It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial).
From the tool's definition Tool name contains 'add' and description states 'Add an input action via editor API', indicating creation/modification of input configuration data that is reversible through the editor.
Attacks that exploit this kind of access
The rule that runs editor_add_input_action 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 editor_add_input_action, this is the rule to start with:
editor_add_input_action stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_add_input_action call is checked against it from then on.
Questions about editor_add_input_action
Add an input action via editor API. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
editor_add_input_action accepts 2 parameters: name, deadzone. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for editor_add_input_action: 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.
editor_add_input_action 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 editor_add_input_action 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 editor_add_input_action. 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.
editor_add_input_action is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue