AI agents call controlGetPos to retrieve information from MCP Windows Desktop Automation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves positional data about UI elements. No modification, execution, deletion, or financial operations are involved. While the description is empty, the naming convention and context within a UI automation suite indicate this is a read-only query operation with minimal security impact. Low severity because positional metadata has no destructive or exploitative potential on its own.
From the tool's definition Tool name 'controlGetPos' indicates retrieval of UI control position information without modification capability.
Documented attack patterns abuse exactly the kind of access controlGetPos gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Windows Desktop Automation, and nothing reaches the server without passing your rules. This is the rule we recommend for controlGetPos:
{
"version": "1",
"default": "deny",
"tools": {
"controlGetPos": {}
}
}controlGetPos is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
controlGetPos. It is categorised as a Read tool in the MCP Windows Desktop Automation MCP Server, which means it retrieves data without modifying state.
Register the MCP Windows Desktop Automation MCP server in PolicyLayer and add a rule for controlGetPos: 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 MCP Windows Desktop Automation. Nothing to install.
controlGetPos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the controlGetPos 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 controlGetPos. 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.
controlGetPos is provided by the MCP Windows Desktop Automation MCP server (mario-andreschak/mcp-windows-desktop-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Windows Desktop Automation, 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.
50 MCP Windows Desktop Automation tools catalogued and risk-classified — across an index of 43,000+ MCP servers.