qa_report

Get the full QA run report including all checks, issues, screenshots, and interaction log.

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-report.md

WHAT IT DOES

What qa_report does on CoWork OS

AI agents call qa_report 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_report is rated Low

The tool retrieves an existing QA report with checks, issues, screenshots, and logs. This is a pure read/query operation with no side effects. Severity is low as it only exposes potentially sensitive internal QA data.

From the tool's definition 'Get the full QA run report including all checks, issues, screenshots, and interaction log'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs qa_report 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_report, this is the rule to start with:

qa_report Allowed

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

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_report call is checked against it from then on.

FAQ

Questions about qa_report

What does the qa_report tool do? +

Get the full QA run report including all checks, issues, screenshots, and interaction log. 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_report? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for qa_report: 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_report? +

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

Can I rate-limit qa_report? +

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

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

qa_report 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

The MCP Attack Database →

Guides

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