Get certificate status
AI agents call get_certificate_status to retrieve information from Domain Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an SSL certificate without modifying, deleting, or executing operations. It retrieves information about an existing certificate, consistent with Read category tools like 'get_domain' and 'list_certificates' on the same server. The blast radius of misuse is minimal—an agent can only view certificate metadata, not modify infrastructure or cause financial harm.
From the tool's definition Tool name 'get_certificate_status' and description 'Get certificate status' indicate a retrieval operation with no side effects. The verb 'Get' and action of checking status are read-only queries.
Attacks that exploit this kind of access
Get certificate status. It is categorised as a Read tool in the Domain Suite MCP Server, which means it retrieves data without modifying state.
Register the Domain Suite MCP server in PolicyLayer and add a rule for get_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 Domain Suite. Nothing to install.
get_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_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_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_certificate_status is provided by the Domain Suite MCP server (oso95/domain-suite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →