update_issue · Helm Chart CLI MCP: Risk & Policy

WHAT IT DOES

What update_issue does on Helm Chart CLI

AI agents use update_issue 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 update_issue needs a policy

This tool modifies existing issues (e.g., status, description, labels) without deleting or destroying them. The changes are reversible—issues can be edited again or reverted. This is a Write operation. Severity is medium because unintended modifications to issues could disrupt workflow coordination and project management, but the impact is limited in scope and reversible.

From the tool's definition Tool name 'update_issue' and description 'Update an existing issue in a GitHub repository' indicate modification of existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_issue Rate-limited

update_issue 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": {
    "update_issue": {
      "limits": [
        {
          "counter": "update_issue_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 update_issue

What does the update_issue tool do? +

Update an existing issue in a GitHub repository. 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 update_issue? +

Register the Helm Chart CLI MCP server in PolicyLayer and add a rule for update_issue: 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 update_issue? +

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

Can I rate-limit update_issue? +

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

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

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