Check screencast recording status: whether recording, frame count, and duration.
AI agents call screencast_status to retrieve information from Chromium ARM64 Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports the state of a screencast recording (whether it is active, frame count, duration). It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. It is a straightforward status check operation, making it a Read category tool with low severity due to its minimal security impact.
From the tool's definition Tool name 'screencast_status' and description 'Check screencast recording status: whether recording, frame count, and duration' indicates a passive query operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Check screencast recording status: whether recording, frame count, and duration. It is categorised as a Read tool in the Chromium ARM64 Browser MCP Server, which means it retrieves data without modifying state.
Register the Chromium ARM64 Browser MCP server in PolicyLayer and add a rule for screencast_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 Chromium ARM64 Browser. Nothing to install.
screencast_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 screencast_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 screencast_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.
screencast_status is provided by the Chromium ARM64 Browser MCP server (nfodor/mcp-chromium-arm64). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →