Low Risk

ssl_certificate_info

Get SSL certificate information for a domain

How to control ssl_certificate_info ↓

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

Low Risk

This tool retrieves publicly available SSL certificate details (issuer, expiration, subject alternative names, etc.) without modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could enumerate certificate data for reconnaissance, but cannot alter or execute anything. This is a standard read/query operation.

From the tool's definition Tool description states 'Get SSL certificate information for a domain' — a retrieval operation with no side effects. It queries and returns existing certificate metadata.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssl_certificate_info": {}
  }
}

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

  1. Create a free account and register Domain-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the ssl_certificate_info tool do? +

Get SSL certificate information for a domain. It is categorised as a Read tool in the Domain-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ssl_certificate_info? +

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

What risk level is ssl_certificate_info? +

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

Can I rate-limit ssl_certificate_info? +

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

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

ssl_certificate_info is provided by the Domain- MCP server (rinadelph/domain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Domain-MCP tool call.

Deterministic rules across all 8 Domain-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 Domain-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.