infra.browser.session_content
Get files downloaded during a browser session — screenshots, PDFs, extracted data (Browserbase)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/infra.browser.session-content.md
What infra.browser.session_content does on Apibase
AI agents call infra.browser.session_content 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 | Session ID to get downloads/content from |
Parameters from the server's own tool schema.
Why infra.browser.session_content is rated Low
Retrieves archived session files and downloads without modifying data or executing new actions.
From the tool's definition Get files downloaded during a browser session
Attacks that exploit this kind of access
The rule that runs infra.browser.session_content 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_content, this is the rule to start with:
infra.browser.session_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every infra.browser.session_content call is checked against it from then on.
Questions about infra.browser.session_content
Get files downloaded during a browser session — screenshots, PDFs, extracted data (Browserbase). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
infra.browser.session_content accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for infra.browser.session_content: 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.
infra.browser.session_content 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 infra.browser.session_content 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 infra.browser.session_content. 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.
infra.browser.session_content 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue