Request user permission to control a set of applications for this session. Must be called before any other tool in this server.
AI agents invoke request_access 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.
This tool triggers an external operation — a permission grant flow that enables subsequent control of desktop applications. While it doesn't directly execute code or modify data, it gates and enables high-impact actions (mouse, keyboard, window control) across applications. Misuse could silently acquire broad desktop control permissions.
From the tool's definition 'Request user permission to control a set of applications for this session. Must be called before any other tool in this server.'
Attacks that exploit this kind of access
Request user permission to control a set of applications for this session. Must be called before any other tool in this server. 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 request_access: 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.
request_access 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 request_access 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 request_access. 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.
request_access 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 →