Execute a JavaScript expression in the page context. The expression is evaluated in the browser and its return value is serialized to JSON. Use this for extracting data, reading page state, or performing custom interactions. You can use fetch() to make HTTP requests from the browser's origin and...
Accepts freeform code/query input (expression)
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 browser_evaluate 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.
browser_evaluate 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:
browser_evaluate:
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 browser_evaluate 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.
browser_evaluate 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.
Execute a JavaScript expression in the page context. The expression is evaluated in the browser and its return value is serialized to JSON. Use this for extracting data, reading page state, or performing custom interactions. You can use fetch() to make HTTP requests from the browser's origin and cookies.. 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 browser_evaluate. 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.
browser_evaluate 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 browser_evaluate 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 browser_evaluate. 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.
browser_evaluate 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.