Bring an application to the front, launching it if necessary. The target application must already be in the session allowlist — call request_access first.
AI agents invoke open_application to trigger actions in Computer Use Windows. 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.
Launching an application is an Execute-category action: it triggers an external process whose effects depend on which application is launched. Misuse could result in launching arbitrary privileged or malicious software, making severity high. The allowlist mitigates but does not eliminate risk.
From the tool's definition 'Bring an application to the front, launching it if necessary' — the tool launches external applications on the Windows desktop
Attacks that exploit this kind of access
Bring an application to the front, launching it if necessary. The target application must already be in the session allowlist — call request_access first. It is categorised as a Execute tool in the Computer Use Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer Use Windows MCP server in PolicyLayer and add a rule for open_application: 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 Computer Use Windows. Nothing to install.
open_application 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 open_application 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 open_application. 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.
open_application is provided by the Computer Use Windows MCP server (wimi321/windows-computer-use-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →