# compliance_check

IT security compliance audit with Qualys SSL Labs grading. Email auth, SSL/TLS, OWASP headers, cookies, privacy, DNSSEC, hosting, data exposure. 8 checks letter graded. Price: $0.15 USDC on Base.

Agent View of the PolicyLayer registry record for `compliance_check`. HTML page: https://policylayer.com/tools/8randonpickart5-alderpost-mcp/compliance-check

## Facts

- Tool: `compliance_check`
- Server: Alderpost (`8randonpickart5/alderpost-mcp`) — https://policylayer.com/tools/8randonpickart5-alderpost-mcp.md
- Homepage: https://github.com/8randonpickart5/alderpost-mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "compliance_check",
    "arguments": {}
  }
}
```

## Why compliance_check is rated Low

This is fundamentally a Read operation: it retrieves and analyzes security posture data from external services (SSL Labs, DNS records, headers) and returns scored audit results. No infrastructure is modified, no data is written or deleted, and no code is executed on target systems. The tool passively evaluates compliance status.

From the tool's own definition: "The tool performs 'IT security compliance audit' with '8 checks letter graded' on SSL/TLS, headers, cookies, DNSSEC, hosting, and data exposure."

## Use case

AI agents call compliance_check to retrieve information from Alderpost 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 Alderpost:

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

## Other tools on Alderpost (7)

- `sports_edge` — Financial — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/sports-edge.md
- `threat_pulse` — Financial — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/threat-pulse.md
- `company_xray` — Read — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/company-xray.md
- `domain_shield` — Read — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/domain-shield.md
- `health_signal` — Read — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/health-signal.md
- `property_intel` — Read — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/property-intel.md
- `prospect_iq` — Read — https://policylayer.com/tools/8randonpickart5-alderpost-mcp/prospect-iq.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=8randonpickart5-alderpost-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/8randonpickart5-alderpost-mcp