Click at the specified screen coordinates.
AI agents invoke click_screen to trigger actions in Computer Control Mcp Lands. 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.
Clicking at screen coordinates is an interactive computer control action that can trigger arbitrary UI operations — submitting forms, pressing buttons, opening files, executing programs, or confirming destructive dialogs. The blast radius is high because an AI agent could misuse it to interact with any on-screen element, potentially causing irreversible or harmful actions depending on what is clicked.
From the tool's definition Click at the specified screen coordinates
Attacks that exploit this kind of access
Click at the specified screen coordinates. It is categorised as a Execute tool in the Computer Control Mcp Lands MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer Control Mcp Lands MCP server in PolicyLayer and add a rule for click_screen: 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 Control Mcp Lands. Nothing to install.
click_screen 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 click_screen 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 click_screen. 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.
click_screen is provided by the Computer Control Mcp Lands MCP server (songcaiya/windows-mcp-lands). 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 →