List certificates within provided namespace_name namespace or within all namespaces if all_namespaces=True (defaults to False, if True ns_name is ignored).
AI agents call list_certificates to retrieve information from Cert Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation typical of listing/fetching actions. Misuse (e.g., an AI agent listing all certificates across namespaces) has minimal blast radius—it gathers information without changing system state. Classified as Read with low severity and high confidence.
From the tool's definition Tool description states 'List certificates' - retrieves or queries certificate data within a namespace or across all namespaces. No modification, deletion, or execution of external operations occurs.
Documented attack patterns abuse exactly the kind of access list_certificates gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cert Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for list_certificates:
{
"version": "1",
"default": "deny",
"tools": {
"list_certificates": {}
}
}list_certificates is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List certificates within provided namespace_name namespace or within all namespaces if all_namespaces=True (defaults to False, if True ns_name is ignored). It is categorised as a Read tool in the Cert Manager MCP Server, which means it retrieves data without modifying state.
Register the Cert Manager MCP server in PolicyLayer and add a rule for list_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 Cert Manager. Nothing to install.
list_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 list_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 list_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.
list_certificates is provided by the Cert Manager MCP server (pibblokto/cert-manager-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cert Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Cert Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.