# delete-project

Delete a project

Agent View of the PolicyLayer registry record for `delete-project`. HTML page: https://policylayer.com/tools/mcp-test-servers/delete-project

## Facts

- Tool: `delete-project`
- Server: Mcp Test Servers (`msfeldstein/mcp-test-servers`) — https://policylayer.com/tools/mcp-test-servers.md
- Homepage: https://github.com/msfeldstein/mcp-test-servers
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete-project",
    "arguments": {}
  }
}
```

## Why delete-project is rated Critical

Deletion operations are classified as Destructive per the schema rules, as they cannot be undone. The high severity reflects that an AI agent misusing this tool could permanently remove entire projects, causing significant data loss. Confidence is 0.95 rather than 1.0 because we lack detail on what 'project' encompasses and whether there are safeguards like soft-deletes, but the explicit 'delete' verb is unambiguous.

From the tool's own definition: "Tool name is 'delete-project' with description 'Delete a project'. The verb 'Delete' combined with 'project' (a likely substantive resource) indicates irreversible removal of data."

## Use case

AI agents call delete-project to permanently remove resources in Mcp Test Servers, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Test Servers:

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

## Other tools on Mcp Test Servers (66)

- `execute-sql` — Execute — https://policylayer.com/tools/mcp-test-servers/execute-sql.md
- `long-running-task` — Execute — https://policylayer.com/tools/mcp-test-servers/long-running-task.md
- `long-running-task-with-message` — Execute — https://policylayer.com/tools/mcp-test-servers/long-running-task-with-message.md
- `long-running-task-with-no-total` — Execute — https://policylayer.com/tools/mcp-test-servers/long-running-task-with-no-total.md
- `ping` — Execute — https://policylayer.com/tools/mcp-test-servers/ping.md
- `start-notification-stream` — Execute — https://policylayer.com/tools/mcp-test-servers/start-notification-stream.md
- `toggle_dynamic_tool` — Execute — https://policylayer.com/tools/mcp-test-servers/toggle-dynamic-tool.md
- `add` — Other — https://policylayer.com/tools/mcp-test-servers/add.md
- `all_types_tool` — Other — https://policylayer.com/tools/mcp-test-servers/all-types-tool.md
- `another-missing-type` — Other — https://policylayer.com/tools/mcp-test-servers/another-missing-type.md
- `bad-param` — Other — https://policylayer.com/tools/mcp-test-servers/bad-param.md
- `crash` — Other — https://policylayer.com/tools/mcp-test-servers/crash.md
- `divide` — Other — https://policylayer.com/tools/mcp-test-servers/divide.md
- `dynamic_feature` — Other — https://policylayer.com/tools/mcp-test-servers/dynamic-feature.md
- `echo` — Other — https://policylayer.com/tools/mcp-test-servers/echo.md
- `echo_structured` — Other — https://policylayer.com/tools/mcp-test-servers/echo-structured.md
- `echo_with_params` — Other — https://policylayer.com/tools/mcp-test-servers/echo-with-params.md
- `env_echo` — Other — https://policylayer.com/tools/mcp-test-servers/env-echo.md
- `fizzbuzz` — Other — https://policylayer.com/tools/mcp-test-servers/fizzbuzz.md
- `format_data` — Other — https://policylayer.com/tools/mcp-test-servers/format-data.md
- `generate_big_response` — Other — https://policylayer.com/tools/mcp-test-servers/generate-big-response.md
- `long_running_progress` — Other — https://policylayer.com/tools/mcp-test-servers/long-running-progress.md
- `many-resources-tool` — Other — https://policylayer.com/tools/mcp-test-servers/many-resources-tool.md
- `missing-type-tool` — Other — https://policylayer.com/tools/mcp-test-servers/missing-type-tool.md
- `multiply` — Other — https://policylayer.com/tools/mcp-test-servers/multiply.md
- `number-param` — Other — https://policylayer.com/tools/mcp-test-servers/number-param.md
- `optionalTool` — Other — https://policylayer.com/tools/mcp-test-servers/optionaltool.md
- `power` — Other — https://policylayer.com/tools/mcp-test-servers/power.md
- `root-echo` — Other — https://policylayer.com/tools/mcp-test-servers/root-echo.md
- `subtract` — Other — https://policylayer.com/tools/mcp-test-servers/subtract.md
- …and 36 more: https://policylayer.com/tools/mcp-test-servers.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=mcp-test-servers · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mcp-test-servers