pages.create
Create a new static website for this Vee3 account. Returns a page id and public URL at {slug}.vee3.site. Deploy uploaded files next with pages.deploy. Cost = 200 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/pages.create.md
What pages.create does on Vee3
AI agents use pages.create to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | object | — | Optional display name for the page. Does not change the public URL. At most 80 characters. |
slug | string | Yes | Page slug used for the public hostname ({slug}.vee3.site). Must be unique across Vee3. Lowercase alphanumeric characters and hyphens only; 1-48 characters; must |
Parameters from the server's own tool schema.
Why pages.create is rated Medium
Creates a new website resource reversibly; no irreversible destruction or financial movement.
From the tool's definition Create a new static website for this Vee3 account
Attacks that exploit this kind of access
The rule that runs pages.create 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.create, this is the rule to start with:
pages.create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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.create call is checked against it from then on.
Questions about pages.create
Create a new static website for this Vee3 account. Returns a page id and public URL at {slug}.vee3.site. Deploy uploaded files next with pages.deploy. Cost = 200 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pages.create accepts 2 parameters: name, slug. Required: slug. 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.create: 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.create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pages.create 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.create. 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.create 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