simulate_mouse_click
Simulate a mouse click at a screen position
This record as markdown: /tools/keeveeg-godot-mcp/simulate-mouse-click.md
What simulate_mouse_click does on Godot
AI agents invoke simulate_mouse_click to trigger actions in Godot. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
button | string | — | Mouse button (default: left) |
pressed | boolean | — | Whether pressed (default: true) |
position | array | Yes | Screen position [x, y] |
Parameters from the server's own tool schema.
Why simulate_mouse_click is rated High
This tool triggers an external operation (simulating user input via mouse click) within a Godot engine environment. Mouse clicks can trigger arbitrary in-editor or in-game actions depending on where the click lands, making this an Execute-category tool with high severity due to the unpredictable and potentially far-reaching effects of simulated input.
From the tool's definition Simulate a mouse click at a screen position
Attacks that exploit this kind of access
The rule that runs simulate_mouse_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For simulate_mouse_click, this is the rule to start with:
simulate_mouse_click stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every simulate_mouse_click call is checked against it from then on.
Questions about simulate_mouse_click
Simulate a mouse click at a screen position. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
simulate_mouse_click accepts 3 parameters: button, pressed, position. Required: position. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for simulate_mouse_click: 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. Nothing to install.
simulate_mouse_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulate_mouse_click 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 simulate_mouse_click. 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.
simulate_mouse_click is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
Across the catalogue