This record as markdown: /tools/yanhuifair-godot-mcp/write-input-action.md
What write_input_action does on Godot
AI agents use write_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 | Input action name (e.g. "jump", "move_left") |
deadzone | object | — | Deadzone for analog inputs (0-1) |
Parameters from the server's own tool schema.
Why write_input_action is rated Medium
This tool creates new input action configurations in Godot, which modifies the project's input system reversibly. It is a Write-category operation (creates/modifies data) rather than Read (it actively changes state) or Execute (it does not run arbitrary code).
From the tool's definition Tool name 'write_input_action' and description 'Create a new input action' indicate creation of configuration data in Godot Engine. The verb 'write' and 'create' establish this as a modification operation.
Attacks that exploit this kind of access
The rule that runs write_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 write_input_action, this is the rule to start with:
write_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 write_input_action call is checked against it from then on.
Questions about write_input_action
Create a new input action. 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.
write_input_action accepts 2 parameters: action, deadzone. 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 write_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.
write_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 write_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 write_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.
write_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