search_certificates
AI agents call search_certificates to retrieve information from Certificate Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries SSL/TLS certificate data from crt.sh for discovery and analysis purposes. No side effects are mentioned or implied—it searches and returns certificate information without creating, modifying, deleting, or executing anything. The minimal information risk and lack of any actionable side effects justify the 'Read' category with low severity.
From the tool's definition Tool name 'search_certificates' combined with server description stating 'certificate search and analysis' and 'domain certificate discovery' indicates a query/retrieval operation.
Attacks that exploit this kind of access
search_certificates. It is categorised as a Read tool in the Certificate Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Certificate Search MCP Server MCP server in PolicyLayer and add a rule for search_certificates: 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 Certificate Search MCP Server. Nothing to install.
search_certificates 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 search_certificates 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 search_certificates. 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.
search_certificates is provided by the Certificate Search MCP Server MCP server (randark-jmt/crt-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 →