# 2aigc_pages_deploy

把静态站点部署到 2AIGC Pages 并返回可分享链接，二选一：① 传 directory（本机磁盘上含 index.html 的构建产物目录绝对路径，同名项目重复部署即更新）；② 传 files=[{path, content}]（把文件内容直接内联，path 为相对路径；二进制用 content_base64）。不要传源码目录，先构建再把产物交给我。

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

## Facts

- Tool: `2aigc_pages_deploy`
- 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: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `files` | array | no | 直接内联的文件列表，需包含 index.html |
| `project` | string | yes | 项目名、子域名或项目 ID（不存在时会自动创建同名项目） |
| `directory` | string | no | 本机磁盘上的构建产物目录绝对路径（仅本机 npx stdio 接入时可用） |

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_deploy",
    "arguments": {
      "project": "<project>"
    }
  }
}
```

## Why 2aigc_pages_deploy is rated High

2aigc_pages_deploy triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Accepts file system path (directory) · Accepts raw HTML/template content (files[].content)

## Use case

AI agents invoke 2aigc_pages_deploy to trigger actions in Pages. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Pages:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "2aigc_pages_deploy": {
      "limits": [
        {
          "counter": "2aigc_pages_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Pages (7)

- `2aigc_pages_delete` — Destructive — https://policylayer.com/tools/2aigc-pages-mcp/2aigc-pages-delete.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