Check the current status of the browser session.
AI agents call browser_status to retrieve information from Daytona Playwright MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries the browser session state with no side effects, fitting the Read category definition. The low severity reflects minimal blast radius—status checks cannot cause harm even if misused by an agent. High confidence due to clear, explicit description of a non-destructive query operation.
From the tool's definition Tool name 'browser_status' and description 'Check the current status of the browser session' indicates a query operation that retrieves session state information without modifying or executing any actions.
Attacks that exploit this kind of access
Check the current status of the browser session. It is categorised as a Read tool in the Daytona Playwright MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Daytona Playwright MCP Server MCP server in PolicyLayer and add a rule for browser_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 Daytona Playwright MCP Server. Nothing to install.
browser_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 browser_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 browser_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.
browser_status is provided by the Daytona Playwright MCP Server MCP server (jamesmurdza/playwright-daytona-mcp-server). 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 →