get_ssl_certificate_status
Get comprehensive SSL certificate status and health check for a hosting package
This record as markdown: /tools/cbrown35-20i-mcp/get-ssl-certificate-status.md
What get_ssl_certificate_status does on 20i MCP Server
AI agents call get_ssl_certificate_status to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_ssl_certificate_status is rated Low
This tool queries and returns status information about SSL certificates. It performs a read-only operation that retrieves data about existing certificates without modifying, deleting, or executing any changes to the hosting infrastructure. Even in a hosting management context, status checks are non-destructive and carry minimal risk when misused by an AI agent, as they cannot alter system state.
From the tool's definition Tool name is 'get_ssl_certificate_status' and description states it 'Get[s] comprehensive SSL certificate status and health check' — purely informational retrieval with no modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_ssl_certificate_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ssl_certificate_status, this is the rule to start with:
get_ssl_certificate_status 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 20i MCP Server, apply this rule, and every get_ssl_certificate_status call is checked against it from then on.
Questions about get_ssl_certificate_status
Get comprehensive SSL certificate status and health check for a hosting package. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_ssl_certificate_status: 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 20i MCP Server. Nothing to install.
get_ssl_certificate_status 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 get_ssl_certificate_status 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 get_ssl_certificate_status. 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.
get_ssl_certificate_status is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue