2aigc_pages_deploy
把静态站点部署到 2AIGC Pages 并返回可分享链接，二选一：① 传 directory（本机磁盘上含 index.html 的构建产物目录绝对路径，同名项目重复部署即更新）；② 传 files=[{path, content}]（把文件内容直接内联，path 为相对路径；二进制用 content_base64）。不要传源码目录，先构建再把产物交给我。
This record as markdown: /tools/2aigc-pages-mcp/2aigc-pages-deploy.md
What 2aigc_pages_deploy does on Pages
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
files | array | — | 直接内联的文件列表，需包含 index.html |
project | string | Yes | 项目名、子域名或项目 ID（不存在时会自动创建同名项目） |
directory | string | — | 本机磁盘上的构建产物目录绝对路径（仅本机 npx stdio 接入时可用） |
Parameters from the server's own tool schema.
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 signalsAccepts file system path (directory) · Accepts raw HTML/template content (files[].content)
Attacks that exploit this kind of access
The rule that runs 2aigc_pages_deploy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pages, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For 2aigc_pages_deploy, this is the rule to start with:
2aigc_pages_deploy stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pages, apply this rule, and every 2aigc_pages_deploy call is checked against it from then on.
Questions about 2aigc_pages_deploy
把静态站点部署到 2AIGC Pages 并返回可分享链接，二选一：① 传 directory（本机磁盘上含 index.html 的构建产物目录绝对路径，同名项目重复部署即更新）；② 传 files=[{path, content}]（把文件内容直接内联，path 为相对路径；二进制用 content_base64）。不要传源码目录，先构建再把产物交给我。. It is categorised as a Execute tool in the Pages MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
2aigc_pages_deploy accepts 3 parameters: files, project, directory. Required: project. The full parameter table on this page comes from the server's own tool schema.
Register the Pages MCP server in PolicyLayer and add a rule for 2aigc_pages_deploy: 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 Pages. Nothing to install.
2aigc_pages_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 2aigc_pages_deploy 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 2aigc_pages_deploy. 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.
2aigc_pages_deploy is provided by the Pages MCP server (@2aigc/pages-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pages, and thousands of servers like it.
This server
Across the catalogue