Low Risk

browserStatus

browserStatus

How to control browserStatus ↓

What browserStatus does on MCP Server Generator

AI agents call browserStatus to retrieve information from MCP Server Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why browserStatus needs a policy

A status check is a non-destructive, read-only operation that retrieves information about the current state of a browser without modifying or executing actions. The empty description reduces confidence slightly, but the semantic meaning of 'Status' strongly implies a query/retrieval operation.

From the tool's definition Tool name 'browserStatus' suggests querying or checking the status of a browser instance. No description provided, but naming convention indicates a status-check operation (read-only).

Documented attack patterns abuse exactly the kind of access browserStatus gives an agent:

How to control browserStatus

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server Generator, and nothing reaches the server without passing your rules. This is the rule we recommend for browserStatus:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browserStatus": {}
  }
}

browserStatus is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Server Generator — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browserStatus

What does the browserStatus tool do? +

browserStatus. It is categorised as a Read tool in the MCP Server Generator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browserStatus? +

Register the MCP Server Generator MCP server in PolicyLayer and add a rule for browserStatus: 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 MCP Server Generator. Nothing to install.

What risk level is browserStatus? +

browserStatus is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browserStatus? +

Yes. Add a rate_limit block to the browserStatus 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.

How do I block browserStatus completely? +

Set action: deny in the PolicyLayer policy for browserStatus. 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.

What MCP server provides browserStatus? +

browserStatus is provided by the MCP Server Generator MCP server (serhatuzbas/mcp-server-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server Generator tool call.

Start from MCP Server Generator, 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.

79 MCP Server Generator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.