Execute sequence of mouse actions (move, click, drag, scroll, wait).
AI agents invoke batch_mouse_actions to trigger actions in OODA Computer Control. 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.
This tool executes real-time mouse operations that interact with the host computer's GUI. While not directly destructive or financial, mouse clicks and drags can trigger arbitrary GUI actions (close windows, submit forms, navigate applications, etc.) whose consequences depend on runtime screen state—a classic Execute category case.
From the tool's definition Tool description states 'Execute sequence of mouse actions (move, click, drag, scroll, wait)'. The verb 'Execute' and the nature of mouse interactions (click, drag) are programmatic actions that trigger external operations whose effects depend on what is on…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_mouse_actions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_mouse_actions:
{
"version": "1",
"default": "deny",
"tools": {
"batch_mouse_actions": {
"limits": [
{
"counter": "batch_mouse_actions_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}batch_mouse_actions 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.
Execute sequence of mouse actions (move, click, drag, scroll, wait). It is categorised as a Execute tool in the OODA Computer Control MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for batch_mouse_actions: 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 OODA Computer Control. Nothing to install.
batch_mouse_actions 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 batch_mouse_actions 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 batch_mouse_actions. 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.
batch_mouse_actions is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.