set · Helm Chart CLI MCP: Risk & Policy

WHAT IT DOES

What set does on Helm Chart CLI

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

WHY IT NEEDS A POLICY

Why set needs a policy

The tool creates or modifies key-value pairs in a Redis data store, which is a reversible write operation. Severity is high because Redis is often used for session storage, caching, and state management; unauthorized writes could corrupt application state, sessions, or cached data that other systems depend on. However, it is not Destructive (data can be overwritten or expired later) and not Financial.

From the tool's definition "Set a Redis key-value pair" — the tool writes/modifies data in Redis with optional expiration control.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set Rate-limited

set 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": {
    "set": {
      "limits": [
        {
          "counter": "set_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 Helm Chart CLI, so you can run agents against it safely.

FAQ

Questions about set

What does the set tool do? +

Set a Redis key-value pair with optional expiration. It is categorised as a Write tool in the Helm Chart CLI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set? +

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

What risk level is set? +

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

Can I rate-limit set? +

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

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

set is provided by the Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.