screen_record_status
Reports whether a recording is active, with the session_id, elapsed_ms, output path, and marker_count.
This record as markdown: /tools/com-local-mcp-local-mcp/screen-record-status.md
What screen_record_status does on Local
AI agents call screen_record_status to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | — |
Parameters from the server's own tool schema.
Why screen_record_status is rated Low
This tool retrieves status information about an ongoing screen recording session (session_id, elapsed_ms, output_path, marker_count). It performs no side effects, does not modify any data, and does not execute code or delete anything. It is a pure read operation that queries the current state of a recording process.
From the tool's definition Tool name 'screen_record_status' and description 'Reports whether a recording is active' indicates querying/retrieving status information without modification or execution of new operations.
Attacks that exploit this kind of access
The rule that runs screen_record_status 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_status, this is the rule to start with:
screen_record_status is read-only, so it stays allowed. 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_status call is checked against it from then on.
Questions about screen_record_status
Reports whether a recording is active, with the session_id, elapsed_ms, output path, and marker_count. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
screen_record_status 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_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 Local. Nothing to install.
screen_record_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the screen_record_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.
Set action: deny in the PolicyLayer policy for screen_record_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.
screen_record_status 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.
This server
Across the catalogue