add_assignees_to_issue · GitHub Project MCP Server MCP

WHAT IT DOES

What add_assignees_to_issue does on GitHub Project MCP Server

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

This tool creates or modifies data reversibly. Adding assignees to an issue is a write operation that changes issue state but does not delete data or execute arbitrary code. The modification is reversible (assignees can be removed).

From the tool's definition The tool name and description indicate it 'Add assignees to an issue' — this modifies an existing issue by adding assignee metadata, a reversible change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_assignees_to_issue Rate-limited

add_assignees_to_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_assignees_to_issue": {
      "limits": [
        {
          "counter": "add_assignees_to_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 add_assignees_to_issue

What does the add_assignees_to_issue tool do? +

Add assignees to an issue. 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_assignees_to_issue? +

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

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

Can I rate-limit add_assignees_to_issue? +

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

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

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

// THE FULL RECORD

add_assignees_to_issue is one line of GitHub Project MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →