qa_screenshot

Take a QA screenshot of the current page with diagnostics.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/qa-screenshot.md

WHAT IT DOES

What qa_screenshot does on CoWork OS

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

RISK

Why qa_screenshot is rated Low

The tool captures a screenshot (read/observe operation) of the current page state along with diagnostic information. It does not modify, delete, or execute anything — it only reads/captures the visual state of a page. Severity is low as it merely observes the current UI state.

From the tool's definition Take a QA screenshot of the current page with diagnostics

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs qa_screenshot safely

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

qa_screenshot Allowed

qa_screenshot 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": {
    "qa_screenshot": {}
  }
}

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

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

FAQ

Questions about qa_screenshot

What does the qa_screenshot tool do? +

Take a QA screenshot of the current page with diagnostics. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qa_screenshot? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for qa_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 CoWork OS. Nothing to install.

What risk level is qa_screenshot? +

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

Can I rate-limit qa_screenshot? +

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

How do I block qa_screenshot completely? +

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

What MCP server provides qa_screenshot? +

qa_screenshot is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

browser_screenshot on Percepta MCP Server → The MCP Attack Database →

Guides

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