k8s_rollout_history | PolicyLayer

WHAT IT DOES

What k8s_rollout_history does on Multi Cluster Kubernetes MCP Server

AI agents call k8s_rollout_history 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.

THE RISK

Low Risk

Why k8s_rollout_history needs a policy

This tool retrieves deployment revision history without modifying, executing, deleting, or financial operations. It is a pure information-gathering operation similar to 'get' or 'list' commands. The low severity reflects minimal blast radius—an AI agent cannot cause operational harm by querying rollout history, and the information returned is typically non-sensitive metadata already accessible within the cluster.

From the tool's definition Tool name 'k8s_rollout_history' and description 'Get the revision history of a deployment, daemonset, or statefulset' indicate a read-only query operation that retrieves historical metadata about Kubernetes resources.

Documented attack patterns abuse exactly the kind of access k8s_rollout_history gives an agent:

POLICY

How to control k8s_rollout_history

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_rollout_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "k8s_rollout_history": {}
  }
}

k8s_rollout_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Multi Cluster Kubernetes MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Multi Cluster Kubernetes MCP Server tools

Destructive k8s_delete_ns Delete a Kubernetes namespace and all resources within it. Destructive k8s_delete_resource Delete a Kubernetes resource. Supports all common resource types Destructive k8s_drain_node Drain a node by evicting all pods, preparing it for maintenance. Execute k8s_pod_exec Execute a command inside a running container. Supports quoted arguments Execute k8s_rollout_restart Trigger a rolling restart of a deployment, daemonset, or statefulset. Execute k8s_run_pod Create and run a pod with the specified container image. Execute k8s_scale_resource Scale a deployment, statefulset, or replicaset to the specified number of replicas. Execute k8s_rollout_pause Pause an in-progress rollout for a deployment, daemonset, or statefulset.

All 57 Multi Cluster Kubernetes MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about k8s_rollout_history

What does the k8s_rollout_history tool do? +

Get the revision history of a deployment, daemonset, or statefulset. It is categorised as a Read tool in the Multi Cluster Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on k8s_rollout_history? +

Register the Multi Cluster Kubernetes MCP Server MCP server in PolicyLayer and add a rule for k8s_rollout_history: 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.

What risk level is k8s_rollout_history? +

k8s_rollout_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit k8s_rollout_history? +

Yes. Add a rate_limit block to the k8s_rollout_history 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.

How do I block k8s_rollout_history completely? +

Set action: deny in the PolicyLayer policy for k8s_rollout_history. 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.

What MCP server provides k8s_rollout_history? +

k8s_rollout_history 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.

Enforce policy on every Multi Cluster Kubernetes MCP Server tool call.

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.

CHECK YOUR STACK →

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.