Get detailed status information for a specific browser
AI agents call get_browser_status to retrieve information from Pydoll without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves/queries the state of a browser instance without performing any actions, modifying data, executing commands, or triggering operations. It is a passive information retrieval operation, fitting the 'Read' category. The low severity reflects that misuse would only expose browser state information with minimal blast radius.
From the tool's definition Tool name is 'get_browser_status' and description states it retrieves 'detailed status information for a specific browser' — a read-only query with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_browser_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for get_browser_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_browser_status": {}
}
}get_browser_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed status information for a specific browser. It is categorised as a Read tool in the Pydoll MCP Server, which means it retrieves data without modifying state.
Register the Pydoll MCP server in PolicyLayer and add a rule for get_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 Pydoll. Nothing to install.
get_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 get_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 get_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.
get_browser_status is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.