AI agents call delete-project to permanently remove resources in GitHub Projects MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a project is an irreversible operation that cannot be undone. It removes all associated data, project structure, and configurations. This falls squarely into the Destructive category. The blast radius is high because an agent could delete a critical project affecting team workflows, losing project history, and requiring administrative recovery.
From the tool's definition Tool name 'delete-project' and description 'Delete a GitHub Project' indicate irreversible deletion of an entire project.
Documented attack patterns abuse exactly the kind of access delete-project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Projects MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-project:
{
"version": "1",
"default": "deny",
"hide": [
"delete-project"
]
}delete-project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a GitHub Project. It is categorised as a Destructive tool in the GitHub Projects MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for delete-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 Projects MCP Server. Nothing to install.
delete-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 delete-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 delete-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.
delete-project is provided by the GitHub Projects MCP Server MCP server (taylor-lindores-reeves/mcp-github-projects). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 GitHub Projects MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 GitHub Projects MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.