infra.browser.session_status

Check the status of a Browserbase session — running, completed, error, timed out. Returns CPU usage, memory, proxy bytes, start/end times (Browserbase)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.browser.session-status.md

WHAT IT DOES

What infra.browser.session_status does on Apibase

AI agents call infra.browser.session_status to retrieve information from Apibase 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	Yes	Browserbase session ID (from create_session result)

Parameters from the server's own tool schema.

RISK

Why infra.browser.session_status is rated Low

Queries session status and metrics; read-only with no side effects or external impact.

From the tool's definition Check the status of a Browserbase session — running, completed, error, timed out. Returns CPU usage, memory, proxy bytes, start/end times

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infra.browser.session_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra.browser.session_status, this is the rule to start with:

infra.browser.session_status Allowed

infra.browser.session_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infra.browser.session_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.browser.session_status call is checked against it from then on.

FAQ

Questions about infra.browser.session_status

What does the infra.browser.session_status tool do? +

Check the status of a Browserbase session — running, completed, error, timed out. Returns CPU usage, memory, proxy bytes, start/end times (Browserbase). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does infra.browser.session_status accept? +

infra.browser.session_status accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on infra.browser.session_status? +

Register the Apibase MCP server in PolicyLayer and add a rule for infra.browser.session_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 Apibase. Nothing to install.

What risk level is infra.browser.session_status? +

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

Can I rate-limit infra.browser.session_status? +

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

How do I block infra.browser.session_status completely? +

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

What MCP server provides infra.browser.session_status? +

infra.browser.session_status is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →