AI agents call browser_sec_get_certificate_info 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 retrieves certificate information from HTTPS sites, which is a non-destructive read operation. It has no side effects, does not execute code, does not modify data, and does not affect financial transactions. The severity is low because certificate information is typically public metadata that an attacker could retrieve through other means (e.g., standard TLS handshake inspection).
From the tool's definition Tool name contains 'get' and description states 'Get TLS/SSL certificate details' — a query operation that retrieves certificate metadata without modifying or executing anything.
Attacks that exploit this kind of access
Get TLS/SSL certificate details for HTTPS sites (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_get_certificate_info: 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_get_certificate_info 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_get_certificate_info 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_get_certificate_info. 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_get_certificate_info 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 →