This record as markdown: /tools/chanceflow-godot-mcp/input-setup-action.md
What input_setup_action does on Godot
AI agents use input_setup_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.
Why input_setup_action is rated Medium
The name 'input_setup_action' suggests creating or configuring input actions in Godot, which would be a reversible modification to game project settings. While the description is empty (reducing confidence), the sibling tools like 'animation_create', 'audio_configure_bus', and 'autoload_add' establish a pattern of Write operations on the project.
From the tool's definition Tool name 'input_setup_action' combined with context of Godot game engine interaction, where 'setup' typically indicates configuration or modification of input actions. The tool appears to create or modify input action mappings.
Attacks that exploit this kind of access
The rule that runs input_setup_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 input_setup_action, this is the rule to start with:
input_setup_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 input_setup_action call is checked against it from then on.
Questions about input_setup_action
input_setup_action is a write tool on the Godot MCP server. 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.
Register the Godot MCP server in PolicyLayer and add a rule for input_setup_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.
input_setup_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 input_setup_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 input_setup_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.
input_setup_action is provided by the Godot MCP server (chanceflow/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