capture_screenshot
Capture the screen to an image file at the given path — writes a file; needs macOS Screen Recording permission. Supports full screen, window, or selection capture.
This record as markdown: /tools/heznpc-airmcp/capture-screenshot.md
What capture_screenshot does on AirMCP
AI agents use capture_screenshot to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why capture_screenshot is rated Medium
The tool captures a screenshot and writes it to a file on disk. This is a Write operation (creates a new file). However, it also involves screen recording which can capture sensitive on-screen information, raising its severity to medium. It is not Execute (no code runs), not Destructive (no deletion), and not Read in the traditional sense since it produces a new artifact on disk.
From the tool's definition Capture the screen to an image file at the given path — writes a file
Attacks that exploit this kind of access
The rule that runs capture_screenshot 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_screenshot, this is the rule to start with:
capture_screenshot stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every capture_screenshot call is checked against it from then on.
Questions about capture_screenshot
Capture the screen to an image file at the given path — writes a file; needs macOS Screen Recording permission. Supports full screen, window, or selection capture. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for capture_screenshot: 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.
capture_screenshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the capture_screenshot 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 capture_screenshot. 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.
capture_screenshot 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.
More on Air, and thousands of servers like it.
This server
Across the catalogue