Low Risk

get_window_info

Retrieve comprehensive information about a specific window using partial title matching, including precise positioning data and calculated center coordinates. Returns detailed JSON with window title, position (x/y), dimensions (width/height), and center point coordinates for precise interaction p...

How to control get_window_info ↓

What get_window_info does on macOS Simulator MCP Server

AI agents call get_window_info to retrieve information from macOS Simulator MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_window_info needs a policy

This tool only queries and returns metadata about macOS windows. It performs no writes, deletions, code execution, or external operations. While it provides data useful for planning interactions (like clicking), the tool itself is strictly informational. The positioning data returned supports Read category classification.

From the tool's definition Tool retrieves window information including 'title, position (x/y), dimensions (width/height), and center point coordinates' with no modification capabilities.

Documented attack patterns abuse exactly the kind of access get_window_info gives an agent:

How to control get_window_info

PolicyLayer is an MCP gateway — it sits between your AI agents and macOS Simulator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_window_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_window_info": {}
  }
}

get_window_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register macOS Simulator MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_window_info

What does the get_window_info tool do? +

Retrieve comprehensive information about a specific window using partial title matching, including precise positioning data and calculated center coordinates. Returns detailed JSON with window title, position (x/y), dimensions (width/height), and center point coordinates for precise interaction planning. More detailed than find_window, providing center coordinates which are essential for reliable clicking on window elements. Use when you need exact positioning data for clicking within a specific window, or for calculating relative coordinates for UI elements. Perfect for planning multi-step interactions within a particular application window. Supports partial title matching for flexibility. It is categorised as a Read tool in the macOS Simulator MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_window_info? +

Register the macOS Simulator MCP Server MCP server in PolicyLayer and add a rule for get_window_info: 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 macOS Simulator MCP Server. Nothing to install.

What risk level is get_window_info? +

get_window_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_window_info? +

Yes. Add a rate_limit block to the get_window_info 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.

How do I block get_window_info completely? +

Set action: deny in the PolicyLayer policy for get_window_info. 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.

What MCP server provides get_window_info? +

get_window_info is provided by the macOS Simulator MCP Server MCP server (ohqay/mac-commander). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every macOS Simulator MCP Server tool call.

Start from macOS Simulator MCP Server, 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.

28 macOS Simulator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.