Inspect security-related HTTP headers (see browser_docs)
AI agents call browser_sec_get_security_headers to retrieve information from Browser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads HTTP security headers from responses. It performs inspection/querying of existing header data without creating, modifying, deleting, or executing any operations. The 'get' verb and 'Inspect' action clearly indicate read-only access. Blast radius is minimal as it only exposes information about security configurations already present in HTTP responses.
From the tool's definition Tool name includes 'get' and description states 'Inspect security-related HTTP headers', indicating data retrieval with no modification or 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 MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Server 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 MCP Server. 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 MCP server (madebytokens/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
browser_sec_get_security_headers is one line of Browser MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →