Search for and locate a specific window using partial title matching, returning detailed window information if found. Supports flexible partial matching - you don
AI agents call find_window 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.
find_window performs window discovery and inspection only. It captures metadata about running windows but does not modify, execute, or control applications. This is equivalent to a search or list operation. The tool has minimal security risk as it only returns information about window state without taking actions.
From the tool's definition Tool description states 'Search for and locate a specific window' and 'returning detailed window information' — retrieval and query operations with no side effects.
Documented attack patterns abuse exactly the kind of access find_window gives an agent:
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 find_window:
{
"version": "1",
"default": "deny",
"tools": {
"find_window": {}
}
} find_window 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.
Search for and locate a specific window using partial title matching, returning detailed window information if found. Supports flexible partial matching - you don. It is categorised as a Read tool in the macOS Simulator MCP Server MCP Server, which means it retrieves data without modifying state.
Register the macOS Simulator MCP Server MCP server in PolicyLayer and add a rule for find_window: 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.
find_window 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 find_window 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 find_window. 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.
find_window 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.
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.