inject_input_event
Injeta um evento de input (mouse/teclado) no jogo EM EXECUÇÃO.
This record as markdown: /tools/mcp-godot-desenvolvimento/inject-input-event.md
What inject_input_event does on Mcp Godot Desenvolvimento
AI agents use inject_input_event to create or update resources in Mcp Godot Desenvolvimento, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Godot Desenvolvimento environment.
Why inject_input_event is rated Medium
An AI agent can call inject_input_event faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Godot Desenvolvimento by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs inject_input_event 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 inject_input_event, this is the rule to start with:
inject_input_event 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 Mcp Godot Desenvolvimento, apply this rule, and every inject_input_event call is checked against it from then on.
Questions about inject_input_event
Injeta um evento de input (mouse/teclado) no jogo EM EXECUÇÃO. It is categorised as a Write tool in the Mcp Godot Desenvolvimento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Godot Desenvolvimento MCP server in PolicyLayer and add a rule for inject_input_event: 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.
inject_input_event 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 inject_input_event 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 inject_input_event. 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.
inject_input_event 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