scan_post_quantum

Check whether a domain's TLS is using post-quantum (hybrid ML-KEM) key exchange.

SERVERFEDLIN Scanners SOURCEhttps://mcp.fedlin.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-fedlin-fedlin-mcp-server/scan-post-quantum.md

WHAT IT DOES

What scan_post_quantum does on FEDLIN Scanners

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

Parameter	Type	Required	Description
`domain`	string	Yes	A bare public hostname to scan, for example example.com. No scheme, path, or port; IP literals and internal hostnames are rejected.

Parameters from the server's own tool schema.

RISK

Why scan_post_quantum is rated Low

Even though scan_post_quantum 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_post_quantum safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FEDLIN Scanners, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_post_quantum, this is the rule to start with:

scan_post_quantum Allowed

scan_post_quantum is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_post_quantum": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FEDLIN Scanners, apply this rule, and every scan_post_quantum call is checked against it from then on.

FAQ

Questions about scan_post_quantum

What does the scan_post_quantum tool do? +

Check whether a domain's TLS is using post-quantum (hybrid ML-KEM) key exchange. It is categorised as a Read tool in the FEDLIN Scanners MCP Server, which means it retrieves data without modifying state.

What parameters does scan_post_quantum accept? +

scan_post_quantum accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on scan_post_quantum? +

Register the FEDLIN Scanners MCP server in PolicyLayer and add a rule for scan_post_quantum: 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 FEDLIN Scanners. Nothing to install.

What risk level is scan_post_quantum? +

scan_post_quantum is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit scan_post_quantum? +

Yes. Add a rate_limit block to the scan_post_quantum 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.

How do I block scan_post_quantum completely? +

Set action: deny in the PolicyLayer policy for scan_post_quantum. 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.

What MCP server provides scan_post_quantum? +

scan_post_quantum is provided by the FEDLIN Scanners MCP server (https://mcp.fedlin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FEDLIN Scanners, and thousands of servers like it.

This server

All 3 FEDLIN Scanners tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →