remove_assignees_from_issue · GitHub Project MCP Server MCP

WHAT IT DOES

What remove_assignees_from_issue does on GitHub Project MCP Server

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

Removing assignees is a reversible modification to an issue's metadata; assignees can be re-added at any time. This is a Write operation, not Destructive, as no data is permanently lost. Misuse could disrupt team workflows by unassigning responsible parties from issues.

From the tool's definition 'Remove assignees from an issue' — modifies an existing issue by removing assigned users

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_assignees_from_issue Rate-limited

remove_assignees_from_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": {
    "remove_assignees_from_issue": {
      "limits": [
        {
          "counter": "remove_assignees_from_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 remove_assignees_from_issue

What does the remove_assignees_from_issue tool do? +

Remove assignees from 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 remove_assignees_from_issue? +

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

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

Can I rate-limit remove_assignees_from_issue? +

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

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

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