screenrecording_status

Report recorder PIDs, the exact Omarchy marker, PID/output ownership, and measured output safety. Read-only.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

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/omarchy-mcp/screenrecording-status.md

WHAT IT DOES

What screenrecording_status does on Omarchy-MCP

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

RISK

Why screenrecording_status is rated Low

Retrieves screen recording status information without modifying system state or triggering actions.

From the tool's definition Report recorder PIDs, exact Omarchy marker, PID/output ownership, measured output safety. Read-only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs screenrecording_status safely

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

screenrecording_status Allowed

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

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

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

FAQ

Questions about screenrecording_status

What does the screenrecording_status tool do? +

Report recorder PIDs, the exact Omarchy marker, PID/output ownership, and measured output safety. Read-only. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on screenrecording_status? +

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

What risk level is screenrecording_status? +

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

Can I rate-limit screenrecording_status? +

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

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

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

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

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