List or update project InputMap actions in project.godot
AI agents use project_input_action to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool performs both read operations (list) and write operations (update) on the InputMap configuration in project.godot. Since it modifies project configuration reversibly, it falls under Write rather than Read. The severity is medium because misconfiguration of input actions could disrupt gameplay or player controls, but the changes are reversible and do not delete data or execute arbitrary code.
From the tool's definition The tool description states it can 'List or update project InputMap actions in project.godot'. The 'update' capability indicates modification of project configuration data.
Documented attack patterns abuse exactly the kind of access project_input_action gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for project_input_action:
{
"version": "1",
"default": "deny",
"tools": {
"project_input_action": {
"limits": [
{
"counter": "project_input_action_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_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.
Free to start. No card required.
List or update project InputMap actions in project.godot. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for project_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 Devtool. Nothing to install.
project_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 project_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 project_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.
project_input_action is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.