Start a cloud browser session via Amazon Bedrock AgentCore. Creates an isolated browser session running in a Firecracker microVM. Returns the session ID and automation stream URL for subsequent browser interaction tools. Usage: 1. Call this tool first to start a browser session. 2. Use the retu...
Part of the AWS Bedrock AgentCore MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke start_browser_session to trigger processes or run actions in AWS Bedrock AgentCore MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
start_browser_session can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
start_browser_session:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.
Agents calling execute-class tools like start_browser_session have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
start_browser_session is one of the high-risk operations in AWS Bedrock AgentCore MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Start a cloud browser session via Amazon Bedrock AgentCore. Creates an isolated browser session running in a Firecracker microVM. Returns the session ID and automation stream URL for subsequent browser interaction tools. Usage: 1. Call this tool first to start a browser session. 2. Use the returned session_id with browser interaction tools (browser_navigate, browser_click, browser_snapshot, etc.). 3. Call stop_browser_session when done.. It is categorised as a Execute tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for start_browser_session. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Bedrock AgentCore MCP Server MCP server.
start_browser_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_browser_session rule in your Intercept 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 Intercept policy for start_browser_session. 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.
start_browser_session is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.