github_issue_track · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What github_issue_track does on Claude Flow

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

WHY IT NEEDS A POLICY

Why github_issue_track needs a policy

The verb 'manage' combined with 'track' indicates the tool creates, updates, or modifies issue state rather than merely retrieving data. This is a Write operation because it likely creates or updates GitHub issues reversibly. It is not Destructive because issue tracking typically allows modifications to be undone.

From the tool's definition Tool name 'github_issue_track' and description phrases 'Track and manage issues' indicate creation, modification, and state management of GitHub issues.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

github_issue_track Rate-limited

github_issue_track 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": {
    "github_issue_track": {
      "limits": [
        {
          "counter": "github_issue_track_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about github_issue_track

What does the github_issue_track tool do? +

Track and manage issues Use when native Bash / file tools are wrong because this MCP tool exposes Ruflo-specific state or controllers that have no shell equivalent. For tasks that fit a one-line native command, prefer that. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_issue_track? +

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

What risk level is github_issue_track? +

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

Can I rate-limit github_issue_track? +

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

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

github_issue_track is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.