Audit security headers of a URL. Checks HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, and cookie security. Returns a score (0-100).
AI agents call header_audit to retrieve information from Mcp Services without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes HTTP security headers from a target URL and returns an assessment score. It performs passive reconnaissance (Read category) with no ability to modify, execute code, delete data, or trigger external state changes. The low severity reflects minimal blast radius if misused—an agent could only scan security posture of websites, which is a passive information-gathering activity.
From the tool's definition Tool description states it 'Audit[s] security headers of a URL' and 'Checks HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, and cookie security.
Attacks that exploit this kind of access
Audit security headers of a URL. Checks HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, and cookie security. Returns a score (0-100). It is categorised as a Read tool in the Mcp Services MCP Server, which means it retrieves data without modifying state.
Register the Mcp Services MCP server in PolicyLayer and add a rule for header_audit: 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 Services. Nothing to install.
header_audit 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 header_audit 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 header_audit. 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.
header_audit is provided by the Mcp Services MCP server (san-npm/mcp-services). 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 →