update-issue · GitHub Enterprise MCP Server MCP

WHAT IT DOES

What update-issue does on GitHub Enterprise MCP Server

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

WHY IT NEEDS A POLICY

Why update-issue needs a policy

This tool modifies issue metadata reversibly. While it can change issue state (open/closed) and content, updates do not destroy data and can be undone by subsequent updates. This makes it Write rather than Destructive. Severity is medium because malicious updates could spam, mislead, or disrupt workflows, but damage is recoverable and scoped to a single repository's issues.

From the tool's definition Tool name 'update-issue' and description 'Update an existing issue in a GitHub repository' indicate modification of existing data. Updates are reversible changes (issue title, description, labels, state) that do not permanently delete data.

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 GitHub Enterprise MCP Server, 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 GitHub Enterprise MCP Server 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 GitHub Enterprise MCP Server 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 GitHub Enterprise MCP Server. 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 GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.