editor_remove_input_action

Remove an input action via editor API.

Server Godot @yanhuifair/godot-mcp
Category Destructive
Risk class Critical
Parameters 11 required

What editor_remove_input_action does on Godot

AI agents call editor_remove_input_action to permanently remove resources in Godot — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
name string Yes

Parameters from the server's own tool schema.

Why editor_remove_input_action needs a policy

This tool deletes an input action from the Godot editor's input map. Removal of a named input action cannot be automatically undone (the action and all its bindings are lost), making it a destructive operation. Severity is medium since it affects project configuration but not code or assets directly.

From the tool's definition 'Remove an input action' — removal is irreversible without manual re-creation

Questions about editor_remove_input_action

What does the editor_remove_input_action tool do? +

Remove an input action via editor API. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does editor_remove_input_action accept? +

editor_remove_input_action accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_remove_input_action? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_remove_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.

What risk level is editor_remove_input_action? +

editor_remove_input_action is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit editor_remove_input_action? +

Yes. Add a rate_limit block to the editor_remove_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.

How do I block editor_remove_input_action completely? +

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

What MCP server provides editor_remove_input_action? +

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

// THE FULL RECORD

editor_remove_input_action is one line of Godot's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.