AI agents call browser_sec_detect_mixed_content to retrieve information from Browser without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs security diagnostics by identifying when HTTPS pages load HTTP resources—a read-only inspection activity. It gathers information about potential security issues but does not execute code, modify data, delete resources, or trigger external operations. The capability is passive analysis aligned with CDP-based diagnostics mentioned in the server description.
From the tool's definition Tool name and description indicate it 'detects' and examines mixed content warnings on pages. The verb 'detect' and the parenthetical '(see browser_docs)' suggest inspection/analysis of existing security state without modifying page behavior, resources, or…
Attacks that exploit this kind of access
Detect mixed content warnings (HTTPS page loading HTTP resources) (see browser_docs). It is categorised as a Read tool in the Browser MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP server in PolicyLayer and add a rule for browser_sec_detect_mixed_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 Browser. Nothing to install.
browser_sec_detect_mixed_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 browser_sec_detect_mixed_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 browser_sec_detect_mixed_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.
browser_sec_detect_mixed_content is provided by the Browser MCP server (ricardodeazambuja/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →