Lists issuers (or cluster issuers) along with their statuses and configuration. If list_cluster_issuers is true, then all_namespaces and namespace_name
AI agents call list_issuers 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 only queries and retrieves metadata about cert-manager issuers and cluster issuers. It performs no write, deletion, execution, or financial operations. The listing of status and configuration information is a read-only operation with minimal blast radius even if invoked incorrectly — the worst outcome is information disclosure of existing issuer configurations, which is already accessible to authenticated…
From the tool's definition Tool name 'list_issuers' and description explicitly states it 'Lists issuers (or cluster issuers) along with their statuses and configuration' — a pure retrieval operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access list_issuers 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_issuers:
{
"version": "1",
"default": "deny",
"tools": {
"list_issuers": {}
}
}list_issuers 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.
Lists issuers (or cluster issuers) along with their statuses and configuration. If list_cluster_issuers is true, then all_namespaces and namespace_name. 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_issuers: 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_issuers 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_issuers 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_issuers. 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_issuers 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.