capture_screen

Capture a full-screen screenshot as a PNG image. Optionally specify a display number for multi-monitor setups (1 = main display). Requires Screen Recording permission.

SERVERAirMCP SOURCEairmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/heznpc-airmcp/capture-screen.md

WHAT IT DOES

What capture_screen does on AirMCP

AI agents call capture_screen to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why capture_screen is rated Low

This tool retrieves visual data from the screen without modifying, deleting, or executing code. It is classified as Read rather than Execute because taking a screenshot is a passive observation operation, not running code or triggering an external operation whose effects depend on arguments.

From the tool's definition capture_screen captures a full-screen screenshot as a PNG image with optional display selection. The description uses passive language (capture, retrieve) indicating data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs capture_screen safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For capture_screen, this is the rule to start with:

capture_screen Allowed

capture_screen is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "capture_screen": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every capture_screen call is checked against it from then on.

FAQ

Questions about capture_screen

What does the capture_screen tool do? +

Capture a full-screen screenshot as a PNG image. Optionally specify a display number for multi-monitor setups (1 = main display). Requires Screen Recording permission. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_screen? +

Register the Air MCP server in PolicyLayer and add a rule for capture_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 AirMCP. Nothing to install.

What risk level is capture_screen? +

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

Can I rate-limit capture_screen? +

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

How do I block capture_screen completely? +

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

What MCP server provides capture_screen? +

capture_screen is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Air, and thousands of servers like it.

This server

All 279 Air tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →