game_input_state
Estado de input: teclas, mouse, gamepad.
This record as markdown: /tools/mcp-godot-desenvolvimento/game-input-state.md
What game_input_state does on Mcp Godot Desenvolvimento
AI agents call game_input_state to retrieve information from Mcp Godot Desenvolvimento without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why game_input_state is rated Low
This tool reads the current state of input devices (keyboard keys, mouse, gamepad). It retrieves data without causing any side effects or modifications. Misuse potential is low as it only exposes input state information.
From the tool's definition Estado de input: teclas, mouse, gamepad — 'Estado' (state) indicates querying/reading current input status
Attacks that exploit this kind of access
The rule that runs game_input_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Godot Desenvolvimento, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For game_input_state, this is the rule to start with:
game_input_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Godot Desenvolvimento, apply this rule, and every game_input_state call is checked against it from then on.
Questions about game_input_state
Estado de input: teclas, mouse, gamepad. It is categorised as a Read tool in the Mcp Godot Desenvolvimento MCP Server, which means it retrieves data without modifying state.
Register the Mcp Godot Desenvolvimento MCP server in PolicyLayer and add a rule for game_input_state: 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 Mcp Godot Desenvolvimento. Nothing to install.
game_input_state 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 game_input_state 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 game_input_state. 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.
game_input_state is provided by the Mcp Godot Desenvolvimento MCP server (joabcostamd/mcp-godot-desenvolvimento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Godot Desenvolvimento, and thousands of servers like it.
This server
Across the catalogue