App
Open/start/launch applications and manage windows. Keywords: open, start, launch, program, application, window, foreground, focus, resize. Three modes:
This record as markdown: /tools/13888285815-windows-mcp/app.md
What App does on Windows-MCP
AI agents invoke App to trigger actions in Windows-MCP. 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.
Why App is rated High
The App tool triggers external operations (application launches and window management) whose effects depend on which application is specified as an argument. This is Execute-category behavior—similar to shell command execution or process spawning. While not inherently destructive, launching applications can have significant side effects (network calls, file modifications, credential access).
From the tool's definition Tool description states it can 'Open/start/launch applications and manage windows' with keywords including 'open, start, launch, program, application'. The ability to launch arbitrary applications on a Windows system represents code/process execution.
Attacks that exploit this kind of access
The rule that runs App safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Windows-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For App, this is the rule to start with:
App 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 Windows-MCP, apply this rule, and every App call is checked against it from then on.
Questions about App
Open/start/launch applications and manage windows. Keywords: open, start, launch, program, application, window, foreground, focus, resize. Three modes:. It is categorised as a Execute tool in the Windows-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Windows MCP server in PolicyLayer and add a rule for App: 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-MCP. Nothing to install.
App 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 App 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 App. 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.
App is provided by the Windows MCP server (13888285815/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Windows, and thousands of servers like it.
Across the catalogue