Low Risk

get_screen_info

Retrieve essential screen dimension information including total width and height in pixels. Critical for coordinate validation before performing clicks, mouse movements, or defining screenshot regions. Returns JSON with screen width and height properties. Use this as the first step in automation ...

How to control get_screen_info ↓

What get_screen_info does on macOS Simulator MCP Server

AI agents call get_screen_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_screen_info needs a policy

get_screen_info is a pure information retrieval operation that queries screen dimensions (width/height in pixels). It has no side effects, does not execute code or commands, does not modify data, and does not perform destructive operations. This is clearly a Read category tool used for informational purposes before other automation steps.

From the tool's definition Tool 'retrieves essential screen dimension information' and 'Returns JSON with screen width and height properties.' It only reads display metadata without modifying, executing operations, or affecting system state.

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

How to control get_screen_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_screen_info:

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

get_screen_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_screen_info

What does the get_screen_info tool do? +

Retrieve essential screen dimension information including total width and height in pixels. Critical for coordinate validation before performing clicks, mouse movements, or defining screenshot regions. Returns JSON with screen width and height properties. Use this as the first step in automation workflows to understand the display boundaries and ensure all coordinates stay within valid ranges. Essential for responsive automation that works across different screen sizes and resolutions. No parameters required - works on primary display. 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_screen_info? +

Register the macOS Simulator MCP Server MCP server in PolicyLayer and add a rule for get_screen_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_screen_info? +

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

Can I rate-limit get_screen_info? +

Yes. Add a rate_limit block to the get_screen_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_screen_info completely? +

Set action: deny in the PolicyLayer policy for get_screen_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_screen_info? +

get_screen_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.