screen_record_stop
Stops the active recording, finalizes the .mov, and writes the marker timeline JSON (§6) next to it. Returns the video path, duration, resolution, marker_count and markers_path. Returns no_active_session if nothing is recording.
This record as markdown: /tools/com-local-mcp-local-mcp/screen-record-stop.md
What screen_record_stop does on Local
AI agents invoke screen_record_stop to trigger actions in Local. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | — | Optional; the single active session is used if omitted. |
Parameters from the server's own tool schema.
Why screen_record_stop is rated High
This tool executes a finalization operation that stops a recording session and persists data (video and JSON marker file) to disk. While not destructive in the sense of deleting data, it is Execute-category because it triggers an external operation with side effects beyond simple read or write.
From the tool's definition Tool performs an action that finalizes and writes files (the .mov video and marker timeline JSON), which are side effects dependent on prior state.
Attacks that exploit this kind of access
The rule that runs screen_record_stop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screen_record_stop, this is the rule to start with:
screen_record_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every screen_record_stop call is checked against it from then on.
Questions about screen_record_stop
Stops the active recording, finalizes the .mov, and writes the marker timeline JSON (§6) next to it. Returns the video path, duration, resolution, marker_count and markers_path. Returns no_active_session if nothing is recording. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
screen_record_stop accepts 1 parameter: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for screen_record_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 Local. Nothing to install.
screen_record_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the screen_record_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.
Set action: deny in the PolicyLayer policy for screen_record_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.
screen_record_stop is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue