add_item_to_project_v2 · GitHub MCP Server MCP

WHAT IT DOES

What add_item_to_project_v2 does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why add_item_to_project_v2 needs a policy

This tool creates or modifies project metadata by adding items to a GitHub Project V2, which is a reversible operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The operation can be undone by removing the item from the project.

From the tool's definition Tool name 'add_item_to_project_v2' and description 'Add an issue or pull request to a GitHub project V2' indicates creation/modification of project state by associating existing items with a project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_item_to_project_v2 Rate-limited

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

FAQ

Questions about add_item_to_project_v2

What does the add_item_to_project_v2 tool do? +

Add an issue or pull request to a GitHub project V2 using GraphQL API. It is categorised as a Write tool in the GitHub 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_item_to_project_v2? +

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

What risk level is add_item_to_project_v2? +

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

Can I rate-limit add_item_to_project_v2? +

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

Set action: deny in the PolicyLayer policy for add_item_to_project_v2. 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_item_to_project_v2? +

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