agent_recording_stop

Stop the in-progress desktop recording and finalize the mp4. Returns { recording:false, id, url, bytes, durationMs } where

SERVEREasyBits SOURCE@easybits.cloud/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/agent-recording-stop.md

WHAT IT DOES

What agent_recording_stop does on EasyBits

AI agents invoke agent_recording_stop to trigger actions in EasyBits. 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 agent_recording_stop is rated High

Stops an active recording process and triggers file finalization on an agent VM.

From the tool's definition Stop the in-progress desktop recording and finalize the mp4

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_recording_stop safely

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

agent_recording_stop Rate-limited

agent_recording_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": {
    "agent_recording_stop": {
      "limits": [
        {
          "counter": "agent_recording_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 EasyBits, apply this rule, and every agent_recording_stop call is checked against it from then on.

FAQ

Questions about agent_recording_stop

What does the agent_recording_stop tool do? +

Stop the in-progress desktop recording and finalize the mp4. Returns { recording:false, id, url, bytes, durationMs } where. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on agent_recording_stop? +

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

What risk level is agent_recording_stop? +

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

Can I rate-limit agent_recording_stop? +

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

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

agent_recording_stop is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits 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 →