# 2aigc_pages_delete

永久删除站点及其全部历史版本，链接立即失效。必须传 confirm=true。下线通常就够了，请慎用。

Agent View of the PolicyLayer registry record for `2aigc_pages_delete`. HTML page: https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-delete

## Facts

- Tool: `2aigc_pages_delete`
- Server: Pages (`@2aigc/pages-mcp`) — https://policylayer.com/tools/2aigc-pages-mcp.md
- Install: `npx -y @2aigc/pages-mcp`
- Homepage: https://www.npmjs.com/package/@2aigc/pages-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `confirm` | boolean | yes | 必须为 true 才会执行删除 |
| `project` | string | yes | 项目名、子域名或项目 ID |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "2aigc_pages_delete",
    "arguments": {
      "confirm": false,
      "project": "<project>"
    }
  }
}
```

## Why 2aigc_pages_delete is rated Critical

An AI agent that decides to call 2aigc_pages_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Pages is gone. There is no undo for destructive operations.

## Use case

AI agents call 2aigc_pages_delete to permanently remove resources in Pages, 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 Pages:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "2aigc_pages_delete"
  ]
}
```

## Other tools on Pages (7)

- `2aigc_pages_deploy` — Execute — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-deploy.md
- `2aigc_pages_list_projects` — Read — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-list-projects.md
- `2aigc_pages_rollback` — Read — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-rollback.md
- `2aigc_pages_status` — Read — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-status.md
- `2aigc_pages_versions` — Read — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-versions.md
- `2aigc_pages_create_project` — Write — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-create-project.md
- `2aigc_pages_set_site` — Write — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-set-site.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=2aigc-pages-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2aigc-pages-mcp