add_issue_to_project · GitHub Project MCP Server MCP

WHAT IT DOES

What add_issue_to_project does on GitHub Project MCP Server

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

This tool performs a create/associate operation that adds data to a GitHub project structure. While it modifies state, the action is reversible (the issue can be removed from the project). It does not execute code, delete resources irreversibly, or affect financial systems.

From the tool's definition 'Add an issue to a GitHub project' - this tool modifies project state by adding/associating an issue, which is a reversible data modification operation. It does not delete, execute arbitrary code, or move money.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_issue_to_project Rate-limited

add_issue_to_project 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_issue_to_project": {
      "limits": [
        {
          "counter": "add_issue_to_project_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 add_issue_to_project

What does the add_issue_to_project tool do? +

Add an issue to a GitHub project. 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 add_issue_to_project? +

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

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

Can I rate-limit add_issue_to_project? +

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

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

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