Release a mouse button at the specified coordinates
AI agents invoke release_mouse to trigger actions in Mcp Autogui Multinode. 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.
Releasing a mouse button is part of a drag-and-drop or click sequence that triggers UI interactions on local or remote systems. It can complete operations like dropping files, confirming dialogs, or finalizing drag actions—making it an Execute-category tool. Misuse by an AI agent could result in unintended UI actions across distributed environments, warranting high severity.
From the tool's definition Release a mouse button at the specified coordinates
Documented attack patterns abuse exactly the kind of access release_mouse gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Autogui Multinode, and nothing reaches the server without passing your rules. This is the rule we recommend for release_mouse:
{
"version": "1",
"default": "deny",
"tools": {
"release_mouse": {
"limits": [
{
"counter": "release_mouse_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}release_mouse 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.
Free to start. No card required.
Release a mouse button at the specified coordinates. It is categorised as a Execute tool in the Mcp Autogui Multinode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Autogui Multinode MCP server in PolicyLayer and add a rule for release_mouse: 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 Autogui Multinode. Nothing to install.
release_mouse 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 release_mouse 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 release_mouse. 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.
release_mouse is provided by the Mcp Autogui Multinode MCP server (stonehill-2345/mcp-autogui-multinode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Autogui Multinode, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Mcp Autogui Multinode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.