http_security_headers
Audit HTTP security headers on a web server. Checks for: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and X-XSS-Protection. Returns which are present with their values, which are missing, and a score.
This record as markdown: /tools/aaronckj-mcp-nettools/http-security-headers.md
What http_security_headers does on Mcp Nettools
AI agents call http_security_headers to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why http_security_headers is rated Low
This tool performs security auditing by querying and analyzing HTTP response headers. It retrieves data about existing security configurations and reports findings without creating, modifying, deleting, or executing any operations. The tool has no blast radius as an AI agent cannot misuse it to cause harm—it only reads and reports on publicly available HTTP header information.
From the tool's definition Tool description states it 'Checks for' and 'Returns which are present with their values' - purely auditing and retrieving information about HTTP security headers on a web server with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs http_security_headers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_security_headers, this is the rule to start with:
http_security_headers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every http_security_headers call is checked against it from then on.
Questions about http_security_headers
Audit HTTP security headers on a web server. Checks for: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and X-XSS-Protection. Returns which are present with their values, which are missing, and a score. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for http_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 Mcp Nettools. Nothing to install.
http_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 http_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 http_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.
http_security_headers is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue