domain_fetch_domain_history
Fetch historical SSL certificate issuance for a domain from Certificate Transparency logs. Read-only. No side effects. Idempotent. domain: Domain name without protocol e.g. example.com. Required. Returns all past certificates with issuer, validity dates, and SANs in reverse chronological order. U...
This record as markdown: /tools/dev-7bd0-mcp-server/domain-fetch-domain-history.md
What domain_fetch_domain_history does on DataNexus MCP
AI agents call domain_fetch_domain_history to retrieve information from DataNexus MCP 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 | — | Domain without protocol e.g. example.com. Required. |
Parameters from the server's own tool schema.
Why domain_fetch_domain_history is rated Low
This tool retrieves historical certificate data from a verified public source (crt.sh) for auditing purposes. It performs a query operation with no capability to alter, delete, or execute code. The blast radius of misuse is minimal—an attacker could only gather information about certificate history, which is already public. Classified as Read with low severity.
From the tool's definition Tool description explicitly states: 'Read-only. No side effects. Idempotent.' It 'Fetch[es] historical SSL certificate issuance' from public Certificate Transparency logs and 'Returns all past certificates'.
Attacks that exploit this kind of access
The rule that runs domain_fetch_domain_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_fetch_domain_history, this is the rule to start with:
domain_fetch_domain_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every domain_fetch_domain_history call is checked against it from then on.
Questions about domain_fetch_domain_history
Fetch historical SSL certificate issuance for a domain from Certificate Transparency logs. Read-only. No side effects. Idempotent. domain: Domain name without protocol e.g. example.com. Required. Returns all past certificates with issuer, validity dates, and SANs in reverse chronological order. Use this to detect domain hijacking or audit unexpected historical certificate issuance. Use domain_fetch_ssl_certificate_chain instead when you only need the current certificate chain. Verified source: crt.sh Certificate Transparency. 4-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="domain_fetch_domain_history", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
domain_fetch_domain_history accepts 1 parameter: domain. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for domain_fetch_domain_history: 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 DataNexus MCP. Nothing to install.
domain_fetch_domain_history 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 domain_fetch_domain_history 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 domain_fetch_domain_history. 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.
domain_fetch_domain_history is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue