add_existing_issue · GitHub Projects MCP Server MCP

WHAT IT DOES

What add_existing_issue does on GitHub Projects MCP Server

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

WHY IT NEEDS A POLICY

Why add_existing_issue needs a policy

This tool creates a new relationship or association in a project management system without deleting or overwriting data. It is reversible (the association can be removed), and does not execute arbitrary code or move money. The blast radius is medium because incorrect usage could clutter projects or associate sensitive issues with unintended projects, but the effect is easily correctable.

From the tool's definition Tool name 'add_existing_issue' and description 'Add an existing issue or pull request to a GitHub Project V2' indicate a create/modify operation that associates an existing issue with a project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_existing_issue Rate-limited

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

FAQ

Questions about add_existing_issue

What does the add_existing_issue tool do? +

Add an existing issue or pull request to a GitHub Project V2. It is categorised as a Write tool in the GitHub Projects 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 add_existing_issue? +

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

What risk level is add_existing_issue? +

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

Can I rate-limit add_existing_issue? +

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

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

add_existing_issue is provided by the GitHub Projects MCP Server MCP server (lexmata/github-projects-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.