AI agents call browser_sec_get_security_headers 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 reads and inspects HTTP security headers from responses. It performs passive information gathering without modifying, executing, or deleting anything. The 'get' verb and 'Inspect' action confirm it is a Read operation. Severity is low because header inspection is non-invasive reconnaissance that does not risk system integrity or data loss.
From the tool's definition Tool name contains 'get' and description states 'Inspect security-related HTTP headers', indicating a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Inspect security-related HTTP headers (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_security_headers: 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_security_headers 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_security_headers 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_security_headers. 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_security_headers 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 →