New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

inject_input_event

Injeta um evento de input (mouse/teclado) no jogo EM EXECUÇÃO.

SERVERMcp Godot Desenvolvimento SOURCEjoabcostamd/mcp-godot-desenvolvimento
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-godot-desenvolvimento/inject-input-event.md

What inject_input_event does on Mcp Godot Desenvolvimento

AI agents invoke inject_input_event to trigger actions in Mcp Godot Desenvolvimento. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why inject_input_event is rated High

This tool injects synthetic input events (mouse/keyboard) into a running game process. It triggers external operations by simulating user interactions at runtime, which can cause arbitrary in-game actions depending on the arguments. This is clearly Execute category — it actively manipulates a running process.

From the tool's definition Injeta um evento de input (mouse/teclado) no jogo EM EXECUÇÃO

Questions about inject_input_event

What does the inject_input_event tool do? +

Injeta um evento de input (mouse/teclado) no jogo EM EXECUÇÃO. It is categorised as a Execute tool in the Mcp Godot Desenvolvimento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on inject_input_event? +

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.

What risk level is inject_input_event? +

inject_input_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit inject_input_event? +

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.

How do I block inject_input_event completely? +

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.

What MCP server provides inject_input_event? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Godot Desenvolvimento's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.