add_input_action
Add a new input action with optional deadzone and event mappings
This record as markdown: /tools/keeveeg-godot-mcp/add-input-action.md
What add_input_action does on Godot
AI agents use 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 |
|---|---|---|---|
action | string | Yes | Action name (e.g. 'jump', 'move_left') |
events | array | Yes | Array of input events to map |
deadzone | number | — | Deadzone value (0-1, default 0.5) |
Parameters from the server's own tool schema.
Why add_input_action is rated Medium
This tool creates or modifies project configuration by adding a new input action, which is a reversible Write operation. While it alters project state, it does not execute arbitrary code, delete data irreversibly, or cause financial impact. The blast radius is medium because misconfigured input actions could affect game functionality or introduce unexpected behavior, but changes can be undone by removing the action.
From the tool's definition Tool name 'add_input_action' and description 'Add a new input action with optional deadzone and event mappings' indicates creation of new input action configuration in a Godot game engine project.
Attacks that exploit this kind of access
The rule that runs 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 add_input_action, this is the rule to start with:
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 add_input_action call is checked against it from then on.
Questions about add_input_action
Add a new input action with optional deadzone and event mappings. 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.
add_input_action accepts 3 parameters: action, events, deadzone. Required: action, events. 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 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.
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 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 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.
add_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.
This server
Across the catalogue