set_input_action
Add or modify an input action and its event mappings
This record as markdown: /tools/keeveeg-godot-mcp/set-input-action.md
What set_input_action does on Godot
AI agents use set_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 |
events | array | Yes | List of input events to map to this action |
deadzone | number | — | Input deadzone value (0-1, default: 0.5) |
Parameters from the server's own tool schema.
Why set_input_action is rated Medium
This tool modifies game input configuration settings, which are data structures that can be created or updated. While this affects game behavior, the changes are reversible and do not execute code, delete data, or cause irreversible damage. It falls into the Write category as a reversible modification operation.
From the tool's definition Tool description states: 'Add or modify an input action and its event mappings'. This indicates modification of game configuration data (input action bindings) which is reversible.
Attacks that exploit this kind of access
The rule that runs set_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 set_input_action, this is the rule to start with:
set_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 set_input_action call is checked against it from then on.
Questions about set_input_action
Add or modify an input action and its 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.
set_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 set_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.
set_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 set_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 set_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.
set_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