# tools_http_header_checker

Free public API. Fetch a URL and return its response headers + security grade based on common security headers.

Agent View of the PolicyLayer registry record for `tools_http_header_checker`. HTML page: https://policylayer.com/tools/dev-domainee-domainee/tools-http-header-checker

## Facts

- Tool: `tools_http_header_checker`
- Server: Domainee (`https://mcp.domainee.dev/mcp`) — https://policylayer.com/tools/dev-domainee-domainee.md
- Homepage: https://github.com/https://mcp.domainee.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | yes | Full URL with scheme, e.g. https://example.com. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "tools_http_header_checker",
    "arguments": {
      "url": "<url>"
    }
  }
}
```

## Why tools_http_header_checker is rated Low

Even though tools_http_header_checker only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Accepts URL/endpoint input (url)

## Use case

AI agents call tools_http_header_checker to retrieve information from Domainee without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Domainee:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tools_http_header_checker": {}
  }
}
```

## Other tools on Domainee (15)

- `tools_cname_lookup` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-cname-lookup.md
- `tools_dkim_record_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-dkim-record-checker.md
- `tools_dmarc_record_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-dmarc-record-checker.md
- `tools_dns_propagation_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-dns-propagation-checker.md
- `tools_dns_record_lookup` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-dns-record-lookup.md
- `tools_domain_age_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-domain-age-checker.md
- `tools_domain_availability_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-domain-availability-checker.md
- `tools_redirect_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-redirect-checker.md
- `tools_reverse_ip_lookup` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-reverse-ip-lookup.md
- `tools_spf_record_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-spf-record-checker.md
- `tools_ssl_check` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-ssl-check.md
- `tools_subdomain_finder` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-subdomain-finder.md
- `tools_txt_record_lookup` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-txt-record-lookup.md
- `tools_website_status_checker` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-website-status-checker.md
- `tools_whois_lookup` — Read — https://policylayer.com/tools/dev-domainee-domainee/tools-whois-lookup.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-domainee-domainee · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-domainee-domainee