AI agents call get_current_context 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.
get_current_context performs no side effects—it only retrieves and returns information about the active Kubernetes context. It does not create, modify, delete, or execute operations. Misuse by an AI agent would have minimal blast radius (information disclosure only). Classified as Read with low severity.
From the tool's definition Tool retrieves the 'current kubeconfig context' without modification or external effects; this is a read-only query operation that returns system state.
Documented attack patterns abuse exactly the kind of access get_current_context 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 get_current_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_context": {}
}
}get_current_context 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.
Get current kubeconfig context. 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 get_current_context: 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.
get_current_context 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_current_context 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_current_context. 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_current_context 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.