Fetch a URL and grade its HTTP security headers (HSTS, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP). Returns a 0–100 score, an A–F grade, and per-header notes. Args: - url (string): URL or host to check (scheme defaults to https://)....
AI agents call http_security_headers to retrieve information from Domain Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a passive security audit tool that retrieves and grades existing HTTP headers. It performs no writes, deletions, external operations, or financial transactions. The blast radius of misuse is minimal—an attacker could check security posture of many domains, but cannot modify headers, execute code, or cause harm via this tool alone. Classified as Read with low severity.
From the tool's definition Tool fetches and analyzes HTTP security headers from a URL and returns a grade/score. The description explicitly states it "Fetch[es] a URL" and "Returns a 0–100 score", indicating read-only retrieval of publicly available HTTP response metadata.
Attacks that exploit this kind of access
Fetch a URL and grade its HTTP security headers (HSTS, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP). Returns a 0–100 score, an A–F grade, and per-header notes. Args: - url (string): URL or host to check (scheme defaults to https://). - response_format (. It is categorised as a Read tool in the Domain Security MCP Server, which means it retrieves data without modifying state.
Register the Domain Security 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 Domain Security. 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 Domain Security MCP server (ortamarco/domain-security-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 →