act
AI agents invoke act to trigger actions in Windows Computer Use. 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.
Given the server's purpose of full Windows desktop control with low-level input injection and the tool name 'act' (implying performing an action), this tool almost certainly executes desktop actions such as mouse clicks, keyboard input, or other UI interactions.
From the tool's definition Tool name 'act' on a server described as enabling 'full control of a Windows desktop with native screen capture, low-level input injection, game-grade input' — sibling tools include 'play', 'process', 'record', 'screenshot', 'system', 'window', suggesting…
Attacks that exploit this kind of access
act. It is categorised as a Execute tool in the Windows Computer Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Windows Computer Use MCP server in PolicyLayer and add a rule for act: 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 Windows Computer Use. Nothing to install.
act 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 act 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 act. 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.
act is provided by the Windows Computer Use MCP server (sshh12/windows-computer-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
act is one line of Windows Computer Use's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →