update_issue · Mcp Github Pm MCP: Risk & Policy

WHAT IT DOES

What update_issue does on Mcp Github Pm

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

WHY IT NEEDS A POLICY

Why update_issue needs a policy

The tool creates or modifies data reversibly within GitHub issues. While it changes state, updates are not destructive — they can be undone or re-edited. This places it firmly in the Write category. Severity is medium because misuse could alter project tracking, assign wrong owners, or close issues prematurely, but the damage is recoverable and the blast radius is limited to a single repository's issues.

From the tool's definition Tool name is 'update_issue' and description states 'Update an existing issue' — this modifies existing data (issue title, description, status, assignee, etc.) in a reversible manner typical of Write operations.

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 Mcp Github Pm, so you can run agents against it safely.

FAQ

Questions about update_issue

What does the update_issue tool do? +

Update an existing issue. It is categorised as a Write tool in the Mcp Github Pm 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 Mcp Github Pm 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 Mcp Github Pm. 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 Mcp Github Pm MCP server (lordbasilaiassistant-sudo/mcp-github-pm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.