update_issue

THE RISK

Medium Risk

Why update_issue needs a policy

This tool modifies an existing issue (title, body, labels, state, assignees, etc.) but does not delete or destroy data. The change is reversible and represents a Write operation. Severity is medium because an AI agent could maliciously alter issue metadata, close legitimate issues, or spam changes, but the blast radius is limited to a single repository's issue tracker and the damage can be undone.

From the tool's definition Tool name 'update_issue' and description 'Update an existing issue in a GitHub repository' indicate modification of existing data. The action is reversible (can be reverted by updating again).

Documented attack patterns abuse exactly the kind of access update_issue gives an agent:

POLICY

How to control update_issue

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub MCP Server Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for update_issue:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_issue": {
      "limits": [
        {
          "counter": "update_issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register GitHub MCP Server Plus — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitHub MCP Server Plus tools

Write add_issue_comment Add a comment to an existing issue Write create_branch Create a new branch in a GitHub repository Write create_issue Create a new issue in a GitHub repository 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_repository Create a new GitHub repository in your account Write fork_repository Fork a GitHub repository to your account or specified organization Write push_files_content Push multiple files with direct content to a GitHub repository in a single commit

All 18 GitHub MCP Server Plus tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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

Enforce policy on every GitHub MCP Server Plus tool call.

Start from GitHub MCP Server Plus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →