Delete a project column
AI agents call delete_project_column to permanently remove resources in GitHub MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a project column from a GitHub project, which cannot be undone. Deletion is irreversible and constitutes data loss. While the blast radius is limited to project organization metadata (not affecting code or critical infrastructure), the action is definitively destructive.
From the tool's definition Tool name is 'delete_project_column' with description 'Delete a project column'. The verb 'delete' combined with the action of removing a project column indicates irreversible data deletion.
Attacks that exploit this kind of access
Delete a project column. It is categorised as a Destructive tool in the GitHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for delete_project_column: 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.
delete_project_column 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 delete_project_column 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 delete_project_column. 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.
delete_project_column 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.
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 →