Helm Chart CLI

88 tools. 40 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated:

40 can modify or destroy data
48 read-only
88 tools total

Community server · catalogue entry verified 05/07/2026

How to control Helm Chart CLI ↓

What Helm Chart CLI exposes to your agents

Read (48) Write / Execute (35) Destructive / Financial (5)
Critical Risk

The most dangerous Helm Chart CLI tools

40 of Helm Chart CLI's 88 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Helm Chart CLI

PolicyLayer is an MCP gateway — it sits between your AI agents and Helm Chart CLI, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add_issue_comment": {
    "limits": [
      {
        "counter": "add_issue_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "brave_local_search": {
    "limits": [
      {
        "counter": "brave_local_search_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Helm Chart CLI — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON HELM CHART CLI →

Instant setup, no code required.

All 88 Helm Chart CLI tools

WRITE 27 tools
Write add_issue_comment Add a comment to an existing issue Write add_observations Add new observations to existing entities in the knowledge graph Write append_insight Add a business insight to the memo Write create_branch Create a new branch in a GitHub repository Write create_directory Create a new directory or ensure a directory exists. Can create multiple Write create_entities Create multiple new entities in the knowledge graph Write create_issue Create a new issue in a GitHub repository Write create_merge_request Create a new merge request in a GitLab project Write create_or_update_file Create or update a single file in a GitHub repository Write create_pull_request Create a new pull request in a GitHub repository Write create_pull_request_review Create a review on a pull request Write create_relations Create multiple new relations between entities in the knowledge graph. Relations should be in active voice Write create_repository Create a new GitHub repository in your account Write create_table Create a new table in the SQLite database Write edit_file Make line-based edits to a text file. Each edit replaces exact line sequences Write fork_repository Fork a GitHub repository to your account or specified organization Write merge_pull_request Merge a pull request Write move_file Move or rename files and directories. Can move files between directories Write push_files Push multiple files to a GitHub repository in a single commit Write set Set a Redis key-value pair with optional expiration Write slack_add_reaction Add a reaction emoji to a message Write slack_post_message Post a new message to a Slack channel Write slack_reply_to_thread Reply to a specific message thread in Slack Write update_issue Update an existing issue in a GitHub repository Write update_pull_request_branch Update a pull request branch with the latest changes from the base branch Write write_file Create a new file or completely overwrite an existing file with new content. Write write_query Execute an INSERT, UPDATE, or DELETE query on the SQLite database
READ 48 tools
Read brave_local_search Searches for local businesses and places using Brave Read brave_web_search Performs a web search using the Brave Search API, ideal for general queries, news, articles, and online conten Read describe_table Get the schema information for a specific table Read directory_tree Get a recursive tree view of files and directories as a JSON structure. Read fetch fetch Read get Get value by key from Redis Read get_file_contents Get the contents of a file or directory from a GitHub repository Read get_file_info Retrieve detailed metadata about a file or directory. Returns comprehensive Read get_issue Get details of a specific issue in a GitHub repository. Read get_pull_request Get details of a specific pull request Read get_pull_request_comments Get the review comments on a pull request Read get_pull_request_files Get the list of files changed in a pull request Read get_pull_request_reviews Get the reviews on a pull request Read get_pull_request_status Get the combined status of all status checks for a pull request Read get_sentry_issue get_sentry_issue Read list List Redis keys matching a pattern Read list_allowed_directories Returns the list of directories that this server is allowed to access. Read list_commits Get list of commits of a branch in a GitHub repository Read list_directory Get a detailed listing of all files and directories in a specified path. Read list_issues List issues in a GitHub repository with filtering options Read list_pull_requests List and filter repository pull requests Read list_tables List all tables in the SQLite database Read maps_directions Get directions between two points Read maps_distance_matrix Calculate travel distance and time for multiple origins and destinations Read maps_elevation Get elevation data for locations on the earth Read maps_geocode Convert an address into geographic coordinates Read maps_place_details Get detailed information about a specific place Read maps_reverse_geocode Convert coordinates into an address Read maps_search_places Search for places using Google Places API Read open_nodes Open specific nodes in the knowledge graph by their names Read puppeteer_screenshot Take a screenshot of the current page or a specific element Read query Run a read-only SQL query Read read_file Read the complete contents of a file from the file system. Read read_graph Read the entire knowledge graph Read read_multiple_files Read the contents of multiple files simultaneously. This is more Read retrieve_from_aws_kb Performs retrieval from the AWS Knowledge Base using the provided query and Knowledge Base ID. Read search Search for files in Google Drive Read search_code Search for code across GitHub repositories Read search_files Recursively search for files and directories matching a pattern. Read search_issues Search for issues and pull requests across GitHub repositories Read search_nodes Search for nodes in the knowledge graph based on a query Read search_repositories Search for GitHub repositories Read search_users Search for users on GitHub Read slack_get_channel_history Get recent messages from a channel Read slack_get_thread_replies Get all replies in a message thread Read slack_get_user_profile Get detailed profile information for a specific user Read slack_get_users Get a list of all users in the workspace with their basic profile information Read slack_list_channels List public or pre-defined channels in the workspace with pagination

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Helm Chart CLI

Can an AI agent delete data through the Helm Chart CLI MCP server? +

Yes. The Helm Chart CLI server exposes 5 destructive tools including delete, delete_entities, delete_observations. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Helm Chart CLI? +

The Helm Chart CLI server has 27 write tools including add_issue_comment, add_observations, append_insight. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Helm Chart CLI.

How many tools does the Helm Chart CLI MCP server expose? +

88 tools across 4 categories: Destructive, Execute, Read, Write. 48 are read-only. 40 can modify, create, or delete data.

How do I enforce a policy on Helm Chart CLI? +

Register the Helm Chart CLI MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Helm Chart CLI tool call.

Deterministic rules across all 88 Helm Chart CLI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

88 Helm Chart CLI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.