check_ssl_certificate
Check if a domain has a valid SSL/TLS certificate and is reachable. Use this to verify a website is serving over HTTPS before making requests. Returns HTTP status and server info. Parameters: domain — Domain to check (e.g. 'example.com').
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/check-ssl-certificate.md
What check_ssl_certificate does on X402 Middleware
AI agents call check_ssl_certificate to retrieve information from X402 Middleware 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 |
Parameters from the server's own tool schema.
Why check_ssl_certificate is rated Low
This tool performs a read-only network check to validate HTTPS connectivity and certificate validity. It queries external information (SSL certificate status, HTTP response) without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal — at worst, an agent could enumerate valid domains or check certificate expiration dates, which are typically public information.
From the tool's definition The tool 'check_ssl_certificate' retrieves and verifies SSL/TLS certificate information and HTTP status for a domain.
Attacks that exploit this kind of access
The rule that runs check_ssl_certificate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_ssl_certificate, this is the rule to start with:
check_ssl_certificate 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 X402 Middleware, apply this rule, and every check_ssl_certificate call is checked against it from then on.
Questions about check_ssl_certificate
Check if a domain has a valid SSL/TLS certificate and is reachable. Use this to verify a website is serving over HTTPS before making requests. Returns HTTP status and server info. Parameters: domain — Domain to check (e.g. 'example.com'). It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
check_ssl_certificate accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for check_ssl_certificate: 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 X402 Middleware. Nothing to install.
check_ssl_certificate 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 check_ssl_certificate 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 check_ssl_certificate. 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.
check_ssl_certificate is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue