pages.deploy
Deploy uploaded account files to a hosted static website. Pass file_name values from files.upload_file / files.list_uploaded_files. Optional path overrides the destination path on the page (defaults to the file basename). Up to 500 files per deploy. Cost = 100 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/pages.deploy.md
What pages.deploy does on Vee3
AI agents invoke pages.deploy to trigger actions in Vee3. 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 | Yes | Files to deploy. Each item is an object with file_name (uploaded account-relative path) and optional path (destination path on the page; defaults to the file ba |
page_id | string | Yes | Page id returned by pages.create. |
Parameters from the server's own tool schema.
Why pages.deploy is rated High
Deploying files to a live website triggers external operations with broad public impact.
From the tool's definition Deploy uploaded account files to a hosted static website
Attacks that exploit this kind of access
The rule that runs pages.deploy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pages.deploy, this is the rule to start with:
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 Vee3, apply this rule, and every pages.deploy call is checked against it from then on.
Questions about pages.deploy
Deploy uploaded account files to a hosted static website. Pass file_name values from files.upload_file / files.list_uploaded_files. Optional path overrides the destination path on the page (defaults to the file basename). Up to 500 files per deploy. Cost = 100 tokens. It is categorised as a Execute tool in the Vee3 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
pages.deploy accepts 2 parameters: files, page_id. Required: files, page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for 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 Vee3. Nothing to install.
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 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 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.
pages.deploy is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue