Low Risk

get_screen_size

Get the dimensions of all connected monitors.

How to control get_screen_size ↓

What get_screen_size does on Openowl

AI agents call get_screen_size to retrieve information from Openowl 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_size needs a policy

This tool retrieves monitor dimensions—metadata about the connected display hardware—with no side effects, state changes, or ability to execute code or modify data. It is purely informational, fitting the Read category for data retrieval operations.

From the tool's definition Tool name 'get_screen_size' and description 'Get the dimensions of all connected monitors' indicate a query operation that retrieves display information without modifying or executing any actions.

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

How to control get_screen_size

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

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

get_screen_size 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 Openowl — 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_size

What does the get_screen_size tool do? +

Get the dimensions of all connected monitors. It is categorised as a Read tool in the Openowl MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_screen_size? +

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

What risk level is get_screen_size? +

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

Can I rate-limit get_screen_size? +

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

Set action: deny in the PolicyLayer policy for get_screen_size. 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_size? +

get_screen_size is provided by the Openowl MCP server (mihir-kanzariya/openowl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openowl tool call.

Start from Openowl, 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.

40 Openowl 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.