patch_storageclass · K8s MCP: Risk & Policy

WHAT IT DOES

What patch_storageclass does on K8s MCP

AI agents use patch_storageclass to create or update resources in K8s MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your K8s MCP environment.

WHY IT NEEDS A POLICY

Why patch_storageclass needs a policy

Patching a StorageClass affects storage configuration across the cluster, potentially impacting how persistent volumes are provisioned and managed for multiple workloads. While reversible (Write category, not Destructive), misuse could degrade storage performance, break volume provisioning, or affect data availability for applications dependent on that storage class.

From the tool's definition Tool name 'patch_storageclass' indicates modification of StorageClass resources. 'Patch' is a reversible update operation that modifies existing configuration rather than creating or deleting resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

patch_storageclass Rate-limited

patch_storageclass stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "patch_storageclass": {
      "limits": [
        {
          "counter": "patch_storageclass_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches K8s MCP, so you can run agents against it safely.

FAQ

Questions about patch_storageclass

What does the patch_storageclass tool do? +

Patch a StorageClass resource. It is categorised as a Write tool in the K8s MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on patch_storageclass? +

Register the K8s MCP server in PolicyLayer and add a rule for patch_storageclass: 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 K8s MCP. Nothing to install.

What risk level is patch_storageclass? +

patch_storageclass is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit patch_storageclass? +

Yes. Add a rate_limit block to the patch_storageclass 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 patch_storageclass completely? +

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

patch_storageclass is provided by the K8s MCP server (rahul007-bit/k8s-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.