certhistory

Cert History: crt.sh issuer timeline & counts

SERVEROsint Terminal SOURCEhttps://osint-mcp.thetempleofdoom.com/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-thetempleofdoom-osint-mcp-osint-terminal/certhistory.md

WHAT IT DOES

What certhistory does on Osint Terminal

AI agents call certhistory to retrieve information from Osint Terminal 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
`q`	string	—

Parameters from the server's own tool schema.

RISK

Why certhistory is rated Low

Even though certhistory 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 certhistory safely

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

certhistory Allowed

certhistory 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": {
    "certhistory": {}
  }
}

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

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

FAQ

Questions about certhistory

What does the certhistory tool do? +

Cert History: crt.sh issuer timeline & counts. It is categorised as a Read tool in the Osint Terminal MCP Server, which means it retrieves data without modifying state.

What parameters does certhistory accept? +

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

How do I enforce a policy on certhistory? +

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

What risk level is certhistory? +

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

Can I rate-limit certhistory? +

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

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

certhistory is provided by the Osint Terminal MCP server (https://osint-mcp.thetempleofdoom.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 Osint Terminal, and thousands of servers like it.

This server

All 474 Osint Terminal tools →

Across the catalogue

The MCP Attack Database →

Guides

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