delete_issue · GitHub Project MCP Server MCP: Risk & Policy

WHAT IT DOES

What delete_issue does on GitHub Project MCP Server

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

WHY IT NEEDS A POLICY

Why delete_issue needs a policy

Despite being named 'delete_issue', the tool actually closes a GitHub issue, which is a reversible action (issues can be reopened). Closing is a state change/write operation, not a true destructive deletion. GitHub's API does not support permanent issue deletion, as confirmed by the description. Severity is medium because closing issues affects project tracking and could disrupt workflows if misused.

From the tool's definition 'Close a GitHub issue (actual deletion not supported by GitHub)' — the tool closes an issue, not deletes it

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

delete_issue Rate-limited

delete_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": {
    "delete_issue": {
      "limits": [
        {
          "counter": "delete_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 Project MCP Server, so you can run agents against it safely.

FAQ

Questions about delete_issue

What does the delete_issue tool do? +

Close a GitHub issue (actual deletion not supported by GitHub). It is categorised as a Write tool in the GitHub Project 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 delete_issue? +

Register the GitHub Project MCP Server MCP server in PolicyLayer and add a rule for delete_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 Project MCP Server. Nothing to install.

What risk level is delete_issue? +

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

Can I rate-limit delete_issue? +

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

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

delete_issue is provided by the GitHub Project MCP Server MCP server (jaqarx/github-project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.