get_domain_intel

ServerCVE MCP Server
CategoryRead

WHAT IT DOES

What get_domain_intel does on CVE MCP Server

AI agents call get_domain_intel to retrieve information from CVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_domain_intel needs a policy

This tool performs reconnaissance-style lookups of publicly available, read-only sources (certificate transparency logs and passive DNS records). It retrieves and correlates existing data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could enumerate subdomains and historical certificates of a target domain, which is informational only.

From the tool's definition Tool retrieves domain intelligence from certificate transparency logs (crt.sh) and passive DNS records (CIRCL PDNS), returning subdomains and certificate history. These are passive, historical records that the tool queries but does not modify.

Documented attack patterns abuse exactly the kind of access get_domain_intel gives an agent:

POLICY

How to control get_domain_intel

PolicyLayer is an MCP gateway — it sits between your AI agents and CVE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_domain_intel:

policy.json

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

get_domain_intel is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register CVE MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CVE MCP Server tools

Read parse_cvss Parse and explain a CVSS vector string (v2, v3.x, or v4.0). Args: vector: CVS Read calculate_risk_score Calculate a composite 0-100 risk score using CVSS, EPSS, KEV, and PoC data. Read check_exploit_availability Search GitHub for public proof-of-concept (PoC) exploit repositories for a CVE. Result Read check_ip_reputation Check an IP address reputation via AbuseIPDB and GreyNoise Community. Returns abuse co Read check_kev Check if a CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog. Args: Read check_package_vulns Check a package for known vulnerabilities via OSV.dev. Args: package: Package Read check_poc_exists Search for proof-of-concept exploits across GitHub, Exploit-DB, and Nuclei templates. Read check_ransomware_intel Check if a Bitcoin address is associated with a known ransomware family using the Rans

All 27 CVE MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_domain_intel

What does the get_domain_intel tool do? +

Get domain intelligence: certificate transparency logs (crt.sh) and passive DNS records (CIRCL PDNS). Returns subdomains and certificate history. Args: domain: Domain name to investigate (e.g. example.com). It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_domain_intel? +

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

What risk level is get_domain_intel? +

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

Can I rate-limit get_domain_intel? +

Yes. Add a rate_limit block to the get_domain_intel 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 get_domain_intel completely? +

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

get_domain_intel is provided by the CVE MCP Server MCP server (mukul975/cve-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CVE MCP Server tool call.

Start from CVE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

27 CVE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.