This record as markdown: /tools/keeveeg-godot-mcp/remove-input-action.md
What remove_input_action does on Godot
AI agents call 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | Action name to remove |
Parameters from the server's own tool schema.
Why remove_input_action is rated Critical
Removing an input action from the InputMap is an irreversible deletion of a named configuration entry. Once removed, the input action binding is gone and would need to be manually recreated. This fits the Destructive category as it permanently deletes data.
From the tool's definition remove_input_action - 'Remove an input action from the InputMap'
Attacks that exploit this kind of access
The rule that runs remove_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 remove_input_action, this is the rule to start with:
remove_input_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every remove_input_action call is checked against it from then on.
Questions about remove_input_action
Remove an input action from the InputMap. 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.
remove_input_action accepts 1 parameter: action. Required: action. 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 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.
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.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
remove_input_action is provided by the Godot MCP server (@keeveeg/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.
Across the catalogue