List Kubernetes Jobs with completion status, active/succeeded/failed counts,
AI agents call k8s_get_jobs to retrieve information from Multi Cluster Kubernetes 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 lists information about Kubernetes Jobs, displaying their status and counts. It performs a read-only query operation with no capability to create, modify, delete, or execute actions. The blast radius is minimal—an AI agent could at worst gather cluster information, which poses low risk.
From the tool's definition Tool name 'k8s_get_jobs' and description 'List Kubernetes Jobs with completion status, active/succeeded/failed counts' indicate retrieval and querying of existing job data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access k8s_get_jobs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Multi Cluster Kubernetes MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for k8s_get_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"k8s_get_jobs": {}
}
} k8s_get_jobs 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 Kubernetes Jobs with completion status, active/succeeded/failed counts,. It is categorised as a Read tool in the Multi Cluster Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi Cluster Kubernetes MCP Server MCP server in PolicyLayer and add a rule for k8s_get_jobs: 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 Multi Cluster Kubernetes MCP Server. Nothing to install.
k8s_get_jobs 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 k8s_get_jobs 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 k8s_get_jobs. 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.
k8s_get_jobs is provided by the Multi Cluster Kubernetes MCP Server MCP server (razvanmacovei/k8s-multicluster-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Multi Cluster Kubernetes MCP Server, 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.
57 Multi Cluster Kubernetes MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.