Remove an issue from a GitHub project
AI agents call remove_issue_from_project to permanently remove resources in GitHub Project MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing an issue from a project dissociates it from the project board, losing its status, position, and project-specific metadata. While the underlying issue still exists, the project association and any project-specific fields/status are lost and may be difficult to fully reconstruct, making this effectively a destructive (irreversible) action at the project-item level.
From the tool's definition 'Remove an issue from a GitHub project' — removal from a project board is typically irreversible without manual re-addition, and could disrupt project tracking
Attacks that exploit this kind of access
Remove an issue from a GitHub project. It is categorised as a Destructive tool in the GitHub Project MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub Project MCP Server MCP server in PolicyLayer and add a rule for remove_issue_from_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.
remove_issue_from_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_issue_from_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.
Set action: deny in the PolicyLayer policy for remove_issue_from_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.
remove_issue_from_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →