Get all input actions and their event bindings from the project Input Map.
AI agents call get_input_actions to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves configuration data (input action mappings) from the Godot project without modifying, deleting, or executing any operations. It is a pure read operation that returns existing project configuration. The blast radius is minimal—an AI agent obtaining this information cannot cause harm, as it merely exposes non-sensitive structural metadata about input bindings.
From the tool's definition Tool name 'get_input_actions' with description 'Get all input actions and their event bindings from the project Input Map' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all input actions and their event bindings from the project Input Map. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for get_input_actions: 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 MCP Server. Nothing to install.
get_input_actions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_input_actions 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 get_input_actions. 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.
get_input_actions is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →