delete-project-field

THE RISK

Critical Risk

Deleting a project field is a destructive operation that irreversibly removes schema data from a GitHub Project. This cannot be undone through the API and would affect all items in the project that use this field. While not as critical as deleting an entire project, field deletion is permanent and impacts project structure.

From the tool's definition Tool name is 'delete-project-field' and description states 'Delete a field from a GitHub Project'. The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete-project-field gives an agent:

HOW TO CONTROL DELETE-PROJECT-FIELD

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-field:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-project-field"
  ]
}

delete-project-field disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register GitHub Projects MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More GitHub Projects MCP Server tools

Destructive delete-project Delete a GitHub Project Destructive delete-project-item Remove an item from a GitHub Project Write clear-item-field-value Clear a field value for an item in a GitHub Project Write add-draft-issue Add a draft issue to a GitHub Project Write add-item-to-project Add an existing issue or PR to a GitHub Project Write archive-project-item Archive an item in a GitHub Project Write bulk-update-project-item-field Update a field value for multiple project items Write convert-draft-issue Convert a draft issue to a regular issue

All 21 GitHub Projects MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in GitHub Projects MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete-project-field tool do? +

Delete a field from 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.

How do I enforce a policy on delete-project-field? +

Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for delete-project-field: 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.

What risk level is delete-project-field? +

delete-project-field is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-project-field? +

Yes. Add a rate_limit block to the delete-project-field 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 delete-project-field completely? +

Set action: deny in the PolicyLayer policy for delete-project-field. 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 delete-project-field? +

delete-project-field 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.

Enforce policy on every GitHub Projects MCP Server tool call.

Deterministic rules across all 21 GitHub Projects MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN GITHUB PROJECTS →

Free to start. No card required.

21 GitHub Projects MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT DELETE-PROJECT-FIELD ON GITHUB PROJECTS MCP SERVER DOES

// THE RISK

// HOW TO CONTROL DELETE-PROJECT-FIELD

// EXPLORE