update_project_v2 · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_project_v2 does on GitHub MCP Server

AI agents use update_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 update_project_v2 needs a policy

This tool modifies GitHub project V2 metadata/configuration through the GraphQL API. Updates are reversible changes to project structure, settings, or properties. While it affects project data and could disrupt workflows if misused, it does not delete data permanently (Destructive) or execute arbitrary code (Execute).

From the tool's definition Tool name contains 'update' and description states 'Update a GitHub project V2'. Update operations modify data reversibly without permanent deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_v2 Rate-limited

update_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": {
    "update_project_v2": {
      "limits": [
        {
          "counter": "update_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 update_project_v2

What does the update_project_v2 tool do? +

Update 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 update_project_v2? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for update_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 update_project_v2? +

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

Can I rate-limit update_project_v2? +

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

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

update_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.