screenrecording_stop

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/screenrecording-stop.md

WHAT IT DOES

What screenrecording_stop does on Omarchy-MCP

AI agents invoke screenrecording_stop to trigger actions in Omarchy-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why screenrecording_stop is rated High

Stops a specific screen recording process and produces an MP4 file output.

From the tool's definition Stop exact recorder PID, signals, marker, output path match

Attacks that exploit this kind of access

RECOMMENDED RULE

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

screenrecording_stop Rate-limited

screenrecording_stop stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "screenrecording_stop": {
      "limits": [
        {
          "counter": "screenrecording_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about screenrecording_stop

What does the screenrecording_stop tool do? +

Stop only the exact recorder PID/start-time identity whose Omarchy marker and output path match. Signals never use global pkill; unrelated recorders are not touched. Requires a cleared unchanged marker and nonempty regular MP4. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screenrecording_stop? +

Register the Omarchy MCP server in PolicyLayer and add a rule for screenrecording_stop: 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_stop? +

screenrecording_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit screenrecording_stop? +

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

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

screenrecording_stop 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 → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →